[JENKINS-34054] Add support for the Docker Notification Plugin - Jenkins Jira

XML

Word

Printable

Details

Type: New Feature
Status: Closed (View Workflow)
Priority: Minor
Resolution: Fixed
Component/s: job-dsl-plugin
Labels:
- job-dsl

Similar Issues:

Show

Description

See https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Hub+Notification

Configuration section

  <triggers>
    <org.jenkinsci.plugins.registry.notification.DockerHubTrigger plugin="dockerhub-notification@2.0">
      <spec></spec>
      <options class="vector">
        <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerForAllUsedInJob/>
        <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames>
          <repoNames>
            <string>testimage</string>
          </repoNames>
        </org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames>
      </options>
    </org.jenkinsci.plugins.registry.notification.DockerHubTrigger>
  </triggers>

Attachments

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

Attachments

Bildschirmfoto 2016-04-06 um 13.09.58.png
63 kB
2016-04-06 11:10

Issue Links

is related to

JENKINS-34105 Add support for parameters of type java.util.Set

Open

Activity

Ascending order - Click to sort in descending order

Christoph Blömer created issue - 2016-04-06 11:10

Christoph Blömer made changes - 2016-04-06 11:50

Field	Original Value	New Value
Description	See https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Hub+Notification	See https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Hub+Notification Confix.xml Code Snippet: {code:xml} <triggers> <org.jenkinsci.plugins.registry.notification.DockerHubTrigger plugin="dockerhub-notification@2.0"> <spec></spec> <options class="vector"> <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerForAllUsedInJob/> <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames> <repoNames> <string>testimage</string> </repoNames> </org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames> </options> </org.jenkinsci.plugins.registry.notification.DockerHubTrigger> </triggers> {code}

Christoph Blömer made changes - 2016-04-06 11:50

Description

See https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Hub+Notification

Confix.xml Code Snippet:
{code:xml}
  <triggers>
    <org.jenkinsci.plugins.registry.notification.DockerHubTrigger plugin="dockerhub-notification@2.0">
      <spec></spec>
      <options class="vector">
        <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerForAllUsedInJob/>
        <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames>
          <repoNames>
            <string>testimage</string>
          </repoNames>
        </org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames>
      </options>
    </org.jenkinsci.plugins.registry.notification.DockerHubTrigger>
  </triggers>
{code}

See https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Hub+Notification

Config.xml Code Snippet:
{code:xml}
  <triggers>
    <org.jenkinsci.plugins.registry.notification.DockerHubTrigger plugin="dockerhub-notification@2.0">
      <spec></spec>
      <options class="vector">
        <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerForAllUsedInJob/>
        <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames>
          <repoNames>
            <string>testimage</string>
          </repoNames>
        </org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames>
      </options>
    </org.jenkinsci.plugins.registry.notification.DockerHubTrigger>
  </triggers>
{code}

Christoph Blömer made changes - 2016-04-06 12:47

Description	See https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Hub+Notification Config.xml Code Snippet: {code:xml} <triggers> <org.jenkinsci.plugins.registry.notification.DockerHubTrigger plugin="dockerhub-notification@2.0"> <spec></spec> <options class="vector"> <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerForAllUsedInJob/> <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames> <repoNames> <string>testimage</string> </repoNames> </org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames> </options> </org.jenkinsci.plugins.registry.notification.DockerHubTrigger> </triggers> {code}	See https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Hub+Notification {code:xmll\|title=Configuration section} <triggers> <org.jenkinsci.plugins.registry.notification.DockerHubTrigger plugin="dockerhub-notification@2.0"> <spec></spec> <options class="vector"> <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerForAllUsedInJob/> <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames> <repoNames> <string>testimage</string> </repoNames> </org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames> </options> </org.jenkinsci.plugins.registry.notification.DockerHubTrigger> </triggers> {code}
Labels		job-dsl

Christoph Blömer made changes - 2016-04-06 12:48

Description

See https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Hub+Notification

{code:xmll|title=Configuration section}
  <triggers>
    <org.jenkinsci.plugins.registry.notification.DockerHubTrigger plugin="dockerhub-notification@2.0">
      <spec></spec>
      <options class="vector">
        <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerForAllUsedInJob/>
        <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames>
          <repoNames>
            <string>testimage</string>
          </repoNames>
        </org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames>
      </options>
    </org.jenkinsci.plugins.registry.notification.DockerHubTrigger>
  </triggers>
{code}

See https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Hub+Notification

{code:xml|title=Configuration section}
  <triggers>
    <org.jenkinsci.plugins.registry.notification.DockerHubTrigger plugin="dockerhub-notification@2.0">
      <spec></spec>
      <options class="vector">
        <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerForAllUsedInJob/>
        <org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames>
          <repoNames>
            <string>testimage</string>
          </repoNames>
        </org.jenkinsci.plugins.registry.notification.opt.impl.TriggerOnSpecifiedImageNames>
      </options>
    </org.jenkinsci.plugins.registry.notification.DockerHubTrigger>
  </triggers>
{code}

Hide

Permalink

Daniel Spilker added a comment - 2016-04-08 14:11

The upcoming Job DSL release will add generic support for any plugin. See https://github.com/jenkinsci/job-dsl-plugin/pull/816 for details.

Here is an example for the generic DSL for the Docker Hub trigger:

job('example') {
  triggers {
    dockerHubTrigger {
      options {
        triggerForAllUsedInJob()
        triggerOnSpecifiedImageNames {
          repoNames(['foo', 'bar'] as Set)
        }
      }
    }
  }
}

It's possible to add symbolic names to the Docker Hub plugin to get a concise DSL. I already did this for the Gerrit Trigger plugin, see https://github.com/jenkinsci/gerrit-trigger-plugin/pull/280.

Show

Daniel Spilker added a comment - 2016-04-08 14:11 The upcoming Job DSL release will add generic support for any plugin. See https://github.com/jenkinsci/job-dsl-plugin/pull/816 for details. Here is an example for the generic DSL for the Docker Hub trigger: job( 'example' ) { triggers { dockerHubTrigger { options { triggerForAllUsedInJob() triggerOnSpecifiedImageNames { repoNames([ 'foo' , 'bar' ] as Set) } } } } } It's possible to add symbolic names to the Docker Hub plugin to get a concise DSL. I already did this for the Gerrit Trigger plugin, see https://github.com/jenkinsci/gerrit-trigger-plugin/pull/280 .

Daniel Spilker made changes - 2016-04-08 14:12

Link

This issue is related to JENKINS-34105 [ JENKINS-34105 ]

Daniel Spilker made changes - 2016-04-18 15:57

Resolution		Fixed [ 1 ]
Status	Open [ 1 ]	Resolved [ 5 ]

Daniel Spilker made changes - 2016-05-08 21:53

Assignee		Daniel Spilker [ daspilker ]
Status	Resolved [ 5 ]	Closed [ 6 ]

R. Tyler Croy made changes - 2016-07-26 00:01

Workflow

JNJira [ 170074 ]

JNJira + In-Review [ 209913 ]

People

Assignee:: Daniel Spilker

Reporter:: Christoph Blömer

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2016-04-06 11:10

Updated:: 2016-05-08 21:53

Resolved:: 2016-04-18 15:57