Uploaded image for project: 'Build'
  1. Build
  2. BUILD-1003

Rollback from triggerRemoteJob plugin to GWT plugin

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • Neutral
    • None
    • None
    • None
    • None

    Description

      As discussed in today's Testing&QA meeting, we uncovered two issues with the triggerRemotePlugin that don't exist with the Generic Webhook Trigger plugin:

      1. when a job on the SRE Jenkins instance is already running, then the plugin offers no option to trigger a job and add it to the queue. Instead, it just quits silently. See log.txt. One possible solution could be to wait for the upstream job to finish, but that's not acceptable because it will slow on premises CI, which is already really long.
      2. when a job on the SRE Jenkins instance is triggered by core CI, we would like to add a text description to state this fact. Currently it's really hard to understand which build comes from the other side. (See screenshot) One needs to match timestamps and triggering user.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                mmichel Maxime Michel
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated: