Hi Kenny
Thanks for your reply.
Unfortunately, the Parameterized Trigger Plugin still forces my original
job to be configured with parameters - My plugin knows the names and
types of the parameters, so it would be tedious for a user to have to set
up the same parameters each time a job is
Linards, if your business is critically depending on this plugins
stability, you should do testing on your side before updating the plugin
anyway.
Besides that, Jenkins developers definitely do not intend to screw up
plugins.
thanks
Christoph
Am 06.05.2013 15:56, schrieb
Thanks,
I was able to install the hpi successfully, and see the visual settings .
Going further , how do we do these things:
1) fortify 360 server url
2) How do we define FPR for uploading it to server.
3) Generating upload token. I can see the help , but where do we need to
run the command?
Hi,
If I could link in the svnkit correction matter I found that in file
svnkit\src\main\java\org\tmatesoft\svn\core\wc\SVNEvent.java there is
something like this:
line 419:
public SVNExternal getExternalInfo() {
return *myExternalInfo*;
}
public SVNExternal
Wouldn't it make more sense to add that functionality to the already existing
Redmine plug-in?
Ulli
Am 09.05.2013 um 07:57 schrieb Louis Henry Nayegon
louis.henry.naye...@gmail.com:
Currently found at https://github.com/louisnayegon/redmine-uploader-plugin
This plugin supports a post build
That's an interesting question. The GitHub plugin doesn't provide a Jenkins
SCM, but it does read the Git SCM URls from projects to interact with GitHub.
Doing what you are talking about would be a bit complex, as logically the
'alternate location' URL (that points to GitHub) would be
If you are triggering a build from within your Action using
the AbstractProject.scheduleBuild()[1] then pass your own generated
ParametersAction, as the third item, containing the required parameters.
Note: Default parameters from the triggered job are not added if they are
not passed in.
Git has the ability to refer to a another local repository when it performs a
clone using the --reference argument to the clone command. The Git plugin
supports that on Unix type systems from the reference setting in the advanced
section of the configuration for each job. I've not been able
'reference' repositories are a very different concept; they aren't a 'master'
repository that can be used instead of the specified one, they are a way to
avoid copying object packs that don't need to be copied.
The GitHub plugin doesn't use the URL in question for Git operations, it uses
the
There is the github URL parameter (link below). It could be used to express
the relationship to the github repo when the Git SCM URI is a mirror.
The logic when interacting with github would look like:
1. Try to parse the github information from the Git SCM URI (as it
currently does).
2. If
Possibly, although I don't know if that would work when the Multiple SCM plugin
is used and multiple Git repositories are used by the project.
- Original Message -
From: jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com
Cc: Kevin Fleming (BLOOMBERG/ 731 LEXIN)
At: May 9
Thanks,
Knowing license used is important for companies. Is it possible to
included the fix in next stable LTS release (1.509.2?)?
Asmund
On Thu, May 9, 2013 at 10:45 PM, Jesse Glick jgl...@cloudbees.com wrote:
On 05/08/2013 03:24 AM, Åsmund Østvold wrote:
My local build version of Jenkins
12 matches
Mail list logo
