Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-75419

v3.6.14 Could not find a job with the identifier

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • rundeck-plugin
    • None
    • Jenkins official docker image v2.440.3
      Rundeck plugin 3.6.14

      I have Jenkins official docker image running in a k8s pod using CasC. Rundeck plugin is configured correctly since it works when clicking test connection. 

      If the pod fails or is moved from a host to another the jobs which use rundeck as a post action have a cached user+password in their config.xml which don't allow them to use the already preconfigured rundeck instance in jenkins > manage > system. If I edit those user password and token and leave them empty all is good, I can save/apply the job. Is there any way to NOT CACHE those creds ? 

      Why do the jobs need parameters user/password/token ? Aren't those established in jenkins > manage> system ? It's like you have a DB configured in Jenkins but you ask for the user/pass for each and every job. Why ?

            vbehar Vincent Behar
            screwyy Adrian Paraschiv
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: