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

A bug while saving the configuration form prevents fingerprinting as a promotion action

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: promoted-builds-plugin
    • Labels:
      None
    • Environment:
      Hudson 1.359, Promoted Builds Plugin 1.7, Ubuntu 10.4, Firefox and Opera.
    • Similar Issues:

      Description

      I am trying to fingerprint a file (date.txt) when a job gets promoted. I added a promotion action to do it and entered "date.txt" in the fingerprinting form that gets created into the promotion box.
      This file is different from the file I fingerprint as a post-build task (revision.txt)
      The problem is: only one setup of the fingerprinting form is saved when I submit my job configuration.
      In other words: if I reload the configuration, the file date.txt appears both in the promotion action fingerprinting form (which is right) and in the post-build fingerprinting form (which is wrong: it should be revision.txt).

      Here is my setup:
      I have 4 jobs:

      • MainTask
      • SubTask1
      • SubTask2
      • DailyRelease

      The first 3 jobs are fingerprinting a file with a revision number (revision.txt), and MainTask gets promoted if both SubTask1 and SubTask2 succeed (and if the fingerprint of their revisions matches).
      If MainTask gets promoted, it should fingerprint a file containing the date (date.txt).

      The last job runs once a day, and always fingerprints a file containing the date (date.txt). It gets promoted if MainTask is successful (and if the fingerprint of their dates matches).

      The purpose of this setup is to have a hierarchical promotion process that returns only one promoted release per day. It was the first idea I came with when I thought about how to achieve such a promotion process.
      I don't know if there are easier ways to do it, but I think the principle it good. It should work, but this bug is preventing it.

        Attachments

          Activity

          fchateau fchateau created issue -
          fchateau fchateau made changes -
          Field Original Value New Value
          Description I am trying to fingerprint a file (date.txt) when a job gets promoted. I added a promotion action to do it and entered "date.txt" in the fingerprinting form that gets created into the promotion box.
          This file is different from the file I fingerprint as a post-build task (revision.txt)
          The problem is: only one setup of the fingerprinting form is saved when I submit my job configuration.
          In other words: if I reload the configuration, the file date.txt appears both in the promotion action fingerprinting form (which is right) and in the post-build fingerprinting form (which is wrong: it should be revision.txt).

          Here is my setup:
          I have 4 jobs:
           - MainTask
           - SubTask1
           - SubTask2
           - DailyRelease
          The first 3 jobs are fingerprinting a file with a revision number (revision.txt), and MainTask gets promoted if both SubTask1 and SubTask2 succeed (and if the fingerprint of their revisions matches).
          If MainTask gets promoted, it should fingerprint a file containing the date (date.txt).

          The last job runs once a day, and always fingerprints a file containing the date (date.txt). It gets promoted if MainTask is successful (and if the fingerprint of their dates matches).

          The purpose of this setup is to have a hierarchical promotion process that returns only one promoted release per day. It was the first idea I came with when I thought about how to achieve such a promotion process.
          I don't know if there are easier ways to do it, but I think the principle it good. It should work, but this bug is preventing it.
          I am trying to fingerprint a file (date.txt) when a job gets promoted. I added a promotion action to do it and entered "date.txt" in the fingerprinting form that gets created into the promotion box.
          This file is different from the file I fingerprint as a post-build task (revision.txt)
          The problem is: only one setup of the fingerprinting form is saved when I submit my job configuration.
          In other words: if I reload the configuration, the file date.txt appears both in the promotion action fingerprinting form (which is right) and in the post-build fingerprinting form (which is wrong: it should be revision.txt).

          Here is my setup:
          I have 4 jobs:
           - MainTask
           - SubTask1
           - SubTask2
           - DailyRelease

          The first 3 jobs are fingerprinting a file with a revision number (revision.txt), and MainTask gets promoted if both SubTask1 and SubTask2 succeed (and if the fingerprint of their revisions matches).
          If MainTask gets promoted, it should fingerprint a file containing the date (date.txt).

          The last job runs once a day, and always fingerprints a file containing the date (date.txt). It gets promoted if MainTask is successful (and if the fingerprint of their dates matches).

          The purpose of this setup is to have a hierarchical promotion process that returns only one promoted release per day. It was the first idea I came with when I thought about how to achieve such a promotion process.
          I don't know if there are easier ways to do it, but I think the principle it good. It should work, but this bug is preventing it.
          fchateau fchateau made changes -
          Environment Ubuntu 10.4, Firefox and Opera Hudson 1.359, Promoted Builds Plugin 1.7, Ubuntu 10.4, Firefox and Opera.
          mindless Alan Harder made changes -
          Assignee mindless [ mindless ]
          scm_issue_link SCM/JIRA link daemon made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          abayer Andrew Bayer made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 136737 ] JNJira + In-Review [ 204195 ]

            People

            Assignee:
            mindless Alan Harder
            Reporter:
            fchateau fchateau
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: