Create options for skipping plugins in <publishers> tag #4

Merged
merged 2 commits into from Dec 17, 2012

Conversation

Projects
None yet
3 participants
Contributor

abangratz commented Dec 17, 2012

If you extend the config (file) by an array of 'skip_plugins' entries, it will try to remove those from the XML configuration template.

Example:

...
  skip_plugins:
    - test
    - parameterizedtrigger.BuildTrigger
    - rubyMetrics.railsStats.RailsStatsPublisher
...

If those options are not given or the XML template misses the <publishers>...</publishers> section, the action will be silently skipped.

No version stuff has been harmed with this pull request.

😉

@pxlpnk pxlpnk added a commit that referenced this pull request Dec 17, 2012

@pxlpnk pxlpnk Merge pull request #4 from abangratz/master
Create options for skipping plugins in <publishers> tag
18935bb

@pxlpnk pxlpnk merged commit 18935bb into pxlpnk:master Dec 17, 2012

1 check passed

default The Travis build passed
Details

armins commented Feb 7, 2013

👍 if you deploy it

armins commented Mar 20, 2013

👍 if we build a config to skip feature branches to deploy on master

armins commented Mar 26, 2013

@pxlpnk: Is it possible to test this on my local dev machine? I really would like to fix the bug (every feature branch deploys on master).
We really use feature branches in our daily workflow.

Owner

pxlpnk commented Mar 26, 2013

@armins of course.
You either let the Kraken run locally on your dev machine and work with the production install of your Jenkins
or you reproduce the complete setup locally (Inkluding jenkins and some repositories with branches)

pxlpnk was assigned Mar 26, 2013

armins commented Mar 26, 2013

Great! Can you provide me some xml config from our jenkins setup or help me setup jenkins locally, too?

On 26.03.2013, at 13:52, Andreas Tiefenthaler notifications@github.com wrote:

@armins of course.
You either let the Kraken run locally on your dev machine and work with the production install of your Jenkins
or you reproduce the complete setup locally (Inkluding jenkins and some repositories with branches)


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment