Hi Krishna
thanks for your answer, but it's not what I'm trying to accpmplish.
I already have jobs statically assigned to nodes through label, what I want
to do is to have a dynamic assignement based on build parameter
Actually I'm trying to use this plugin
https://wiki.jenkins-ci.org/display/
Hi all
is there a way/plugin to be able to force build node depending on a build
parameter?
I have production/staging/test profiles and I'd like to have different
slaves in different sub-network to deploy them but I do not want to create
3 different job for this.
thanks in advance
submit both name
and goal as normal parameters, no json.
This seems to work fine with both GET or POST methods, even using basic
login/pass or login/token authentication
On Thursday, June 28, 2012 11:34:29 AM UTC+2, Michele Sacchetti wrote:
>
> a small add-on, the problem seems to be rela
a small add-on, the problem seems to be related to the fact that the field
is of type "List Subversion type" instead of a simple string.
POST is working fine if i switch type to string , maybe I have to specify
other values other then simple name/value ?
Hi All
I'm trying to trigger a build from a java client through Rest API
the build is parametrized:
- tag : SVN tag
- goal : maven goal
I submit a POST to the build URL with such parameters
INFO: url:[http://ci.mydomain/job/myjob/build]
INFO: POST
data:[json={"parameter":[{"name":"tag"
erformed
> manually? If so, it would make more sense to put this into your deployment
> tool, not in Jenkins.
>
> -- Dean
>
> On 4/19/12 1:26 AM , "Michele Sacchetti"
> wrote:
>
>
>
>
>
>
>
> > Hi all
>
> > I'd like to introduce a s
Hi all
I'd like to introduce a sort of external validation on jenkins build.
Basically all I want to do is have people compile a "release form" on
a ticketing tool (redmine,RT,etc. i do not care)
Such ticketing tool can expose ticket status through web service/REST
so it can be checked by http.
