Hi All,
I'm having trouble with this build pipeline:
http://jenkins.simplistix.co.uk/view/testfixtures/
So, what I want is:
- testfixtures-buildout (the initial job)
- testfixtures-tox and testfixtures-docs are downstream jobs that run if
-buildout succeeds (this bit is working)
- If all the above succeeds, testfixtures-release needs to be manually
triggered (this works), preferably from the pipeline view (this doesn't)
So, firstly, I use the build promotion plugin, with a manual approve
step in testfixtures-buildout to trigger testfixtures-release. This is
actually working; I thought it wasn't, but it's just the build promotion
UI isn't that intuitive...
However, it doesn't seem like the pipeline view plugin looks at the
promotion plugin's config at all. Have I got that right? If so, it would
be great if it could look at the promotion plugin config, see there's a
manual step, and add a button where appropriate. Don't suppose the
Centrum guys are working on that?
So, in the absence of that, I configured a "Build Pipeline Plugin ->
Manually Execute Downstream Project" of testfixtures-release on
testfixtures buildout. I think this has worked, but produces a weird
layout on http://jenkins.simplistix.co.uk/view/testfixtures/
How can I get testfixtures-release to show up in a 4th column to the
right of testfixures-docs rather than in the 3rd column below
testfixtures-docs?
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
