Comments for Centrum Systems

Comment on Build Pipeline Plugin Release 1.2.2 by Zachary Young

Zachary Young — Fri, 30 Mar 2012 00:23:17 +0000

At the very least, you create a “Pipeline” view, not a job.

Comment on Build Pipeline Plugin Release 1.2.2 by Marcos Sousa

Marcos Sousa — Wed, 14 Mar 2012 17:16:12 +0000

I’m trying to use this plugin but I’m facing some trouble… I’m not seeing Build Pipeline View in the new job wizard. Is there any configuration to be made? I’m using Pipeline plugin 1.2.3 and Jenkins 1.447. Thanks

Comment on Build Pipeline Plugin Release 1.2.2 by Bedwyr Humphreys

Bedwyr Humphreys — Tue, 14 Feb 2012 16:50:39 +0000

I get around this by writing these values to a property file which i then copy over to the downstream job using copy artifacts plugin.

Comment on Build Pipeline Plugin Release 1.2.2 by Michael Schmook

Michael Schmook — Wed, 23 Nov 2011 10:57:14 +0000

I find the Build Pipeline Plugin a great tool to setup a full deployment pipeline. Are you still working on this plugin, or has the project died?

I noticed that a lot of people (me included) ran into the problem of not being able to pass parameters to manually triggered downstream jobs. Is there a solution for this planned?

The manually triggered downstream jobs are a great part of the plugin, but rather useless if theres no way to retrieve informations from the particular upstream job, like the svn revision number that was used in the pipeline run.

Comment on Build Pipeline Plugin Release 1.1.1 by vishnu

vishnu — Thu, 18 Aug 2011 18:20:22 +0000

Hi
I really like this plugin. But I have not figured out how to let the downstream build know which upstream build triggered it. Is there a way to pass artifacts downstream? or my source control revision number (so I check out the same revision)?

Comment on Coding standards harmony by Sonar » Sonar in the news

Sonar » Sonar in the news — Tue, 07 Jun 2011 09:27:35 +0000

[...] Coding Standards Harmony By Marcin Popielarz, 6 May 2011 Most mature software development companies or departments define their coding standards. The intentions is simple; ensure all code looks alike to ease reading, writing, maintaining and communicating code. As a first effort, these coding conventions may be expressed in some form of standalone document, but conventions that are not being enforced are simply a waste of time… [...]

Comment on BUILD PIPELINE PLUGIN RELEASE 1.1.2 by Geoff Bullen

Geoff Bullen — Wed, 01 Jun 2011 04:44:52 +0000

Looking forward to it!

Comment on BUILD PIPELINE PLUGIN RELEASE 1.1.2 by Geoff Bullen

Geoff Bullen — Wed, 01 Jun 2011 04:44:00 +0000

1) The revision number is retrieved using the remote access API at the moment as there is no easy way to get at it from the core. Because of this, the anonymous user needs to be granted read access
2) Interesting idea, perhaps you could raise an enhancement request – http://code.google.com/p/build-pipeline-plugin/issues/list . Or, better still, submit a patch!

Comment on BUILD PIPELINE PLUGIN RELEASE 1.1.2 by Jaakko Aro

Jaakko Aro — Sat, 28 May 2011 10:52:52 +0000

Hi,

The regex -stuff works already, but i still need to implement all the necessary stuff so that it handles situations like project renaming etc. correctly. Most of the functionality is already implemented, so it shouldn’t take so long, but it depends when I got time to finish it.. Also the tests have to be refactored

Comment on BUILD PIPELINE PLUGIN RELEASE 1.1.2 by Paul Marshall

Paul Marshall — Wed, 18 May 2011 08:18:09 +0000

Just downloaded 1.1.2 of Build Pipeline PlugIn for Hudson.
Looks great, thanks.
1) How is the “revision” populated (grey box against each pipeline)?
2) With a long pipeline, not all the stages can fit on one page when shown on an “information radiator”. The content of each stage instance could be configurable i.e the default is to show the job name, build number and duration, but I may only want to show the build number, thus reducing the size of the block.

Let me know….