Parameterized build, REST, one parameter with new value rest with default

[Daniel Olausson]

Hi,

I have a job that I would like to trigger via REST where I have one 
parameter that I want to change every time and the other ones I would like 
to use the default values for. If I do a POST to /build it just ignores the 
default values and set them to empty. If I do a post to 
/buildWithParameters I can't set the new value for the parameter I want, 
the default values for all parameters are taken.

How can I achieve this? First do a GET to get the default values, and then 
do a POST to /build with all the parameters even if they are just the 
default? 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1a9bc9c4-be67-4549-8fd2-99ed92827bf7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline: Using notifyCommit does not indicate an SCM change

[Sverre Moe]

Created
https://issues.jenkins-ci.org/browse/JENKINS-37406

mandag 15. august 2016 06.30.34 UTC+2 skrev James Dumay følgende:
>
> Hi Sverre,
>
> Hmm, that doesn't sound like we are doing the right thing there. Could you 
> please provide us with a detailed bug report on 
> https://issues.jenkins-ci.org ? Any reproduction steps, examples, 
> screenshots, etc would be greatly appreciated. 
>
> On Friday, August 12, 2016 at 4:50:22 PM UTC+10, Sverre Moe wrote:
>>
>> There is no longer an SCM change when using Multibranch Pipeline.
>> "Started by an SCM change"
>>
>> Instead when the git server executes notifyCommit the branch that has 
>> changes shows "Branch indexing" and a question mark. Though at least the 
>> changes from SCM are shown on each build.
>>
>> Its just that Branch indexing with a Question mark does not look good. 
>> Though when the build completes the question mark is gone. Better yet the 
>> --/++ badge icon indicating an SCM change should be used. At least when I 
>> start a build manually it shows "Started by user *" as tooltip on the 
>> user badge icon.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ca9589f8-ca0f-45e9-a7db-6f68d9571f7d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipelines, github fork models and the Jenkinfile

[Arvind Jayaprakash]

It appears that having the ghprb trigger be pipeline compatible might solve 
my problems. Most of the other triggers seem to have been ported 

 
to be pipeline compatible.

On Saturday, August 13, 2016 at 9:02:07 PM UTC+5:30, Arvind Jayaprakash 
wrote:
>
> I seem to have developed a love/hate relationship with Jenkins 2.x 
> pipelines and some of the concepts that it imposes. Hence, I'd like to hear 
> how best operate in the new world. The one thing I'd like to make clear 
> before I get into the details is that I am suggesting that this the only 
> right way to do things; all I am looking to hear is Jenkins 2.x would be 
> able to support this as one of the many models.
>
> Firstly, let me describe the development model that I'd like to work with. 
> The setup I have is very similar to how a lot of github bases open source 
> projects operate i.e. the main repo very rarely has any branches. All 
> development is done by forking the code, making any number of branches 
> within forks and finally submitting a pull request to the *main/parent* git 
> repository. There is a fairly elaborate acceptance criteria for a pull 
> request to be accepted into the mainline and this is the workflow that I'd 
> like to trigger and run as a pipeline. The way I have been doing this until 
> now is by having a github pull request builder 
> 
>  
> triggered job that sets of a series of steps within a freestyle job and 
> then having downstream jobs associated with it. It is not clear as to how 
> one would setup something using the pipeline construct.
>
> Secondly, I do not wish to provide the flexibility of defining the 
> pipeline (at least in it's current form) to individual developers. The 
> design choice of needing a Jenkinsfile in the each git repo (and branch) 
> seems equivalent to allowing developers to define their own freestyle jobs 
> in Jenkins 1.x. The model that I have been following is to have a 
> predefined set of templates (setup using the Job DSL 
> ) from which 
> the developer can choose along with a minimal set of parameters such as the 
> path of the git repo, the email addresses for notification, choice of JRE, 
> etc. etc. to instantiate specific jobs for their code bases. I'd like to 
> retain this degree of control/standardization as we move into Jenkins 2.x.
>
> In short, I am looking for a way by which I can confine myself to the fork 
> model of git development, pull request based triggers, and job definitions 
> as pipelines, with the pipeline definition residing on jenkins (and not the 
> developer's source tree).
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e53a5746-f373-4701-b206-d7ad3e7e1de2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline: Using notifyCommit does not indicate an SCM change

[James Dumay]

Hi Sverre,

Hmm, that doesn't sound like we are doing the right thing there. Could you 
please provide us with a detailed bug report 
on https://issues.jenkins-ci.org ? Any reproduction steps, examples, 
screenshots, etc would be greatly appreciated. 

On Friday, August 12, 2016 at 4:50:22 PM UTC+10, Sverre Moe wrote:
>
> There is no longer an SCM change when using Multibranch Pipeline.
> "Started by an SCM change"
>
> Instead when the git server executes notifyCommit the branch that has 
> changes shows "Branch indexing" and a question mark. Though at least the 
> changes from SCM are shown on each build.
>
> Its just that Branch indexing with a Question mark does not look good. 
> Though when the build completes the question mark is gone. Better yet the 
> --/++ badge icon indicating an SCM change should be used. At least when I 
> start a build manually it shows "Started by user *" as tooltip on the 
> user badge icon.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/11e39069-ac72-4c76-8393-a1142bfee1dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Stash Integration with Jenkins Pipeline {for Code Review}

[James Dumay]

You need the Bitbucket Branch source plugin which works with Bitbucket 
Cloud and Bitbucket Server (was Stash) 
https://wiki.jenkins-ci.org/display/JENKINS/Bitbucket+Branch+Source+Plugin

The user guide can be found 
here 
https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/chapter-bitbucket.html
 

Interested to know what your milage is like so do drop a reply here if it 
works for you or if you have any troubles :)


On Friday, August 12, 2016 at 12:17:14 PM UTC+10, Sajith Majeed - Saaj 
wrote:
>
> We are trying to implement a code review process for our applications. We 
> use GIT repository and Atlassian Stash.
>
> 1. Have any of you integrated Stash Pull requests with Jenkins Pipelines ? 
> Are there any plugins or documentations that are available to do this ?
> 2. Is there a better code review process with Pull request that can be 
> integrated to Jenkins Pipelines?
>
>
> Thanks | Sajith
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f1f66579-959e-442a-810d-35fc6870c6c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: The option to “Launch slave agents via Java Web Start” is missing from new node configuration

[Ryan Campbell]

I agree. This is impossible to discover for new or even experienced users.

On Sun, Aug 14, 2016, 7:25 PM Richard Bywater  wrote:

> Perhaps it would be an idea to show the item but as disabled and state
> what actions are required to get it enabled?
>
> Richard.
>
> On Mon, 15 Aug 2016 at 12:15 Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
>> So the logic here is to reflect that the TCP agent port has been disabled
>> and thus the launcher is not available to you.
>>
>> On 4 August 2016 at 11:47, Kumar Dp  wrote:
>>
>>> I'm trying to configure a salve using "Launch slave agents via Java Web
>>> Start", but I see that option is not listed in the launch method. I'm using
>>> Jenkins 2.14 version.OS: Linux 3.8.13-68.3.4.el6uek.x86_64
>>> Please help me to solve the issue
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/21bef93a-67f6-4eb4-887b-ea1bc7d5f6cd%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMzbwTVUYGXuuZ1vx52rcj_G26LjWJkt24KVE%3DC1bJ2t0Q%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAMui945xtpCZ-SjuuuUrGvmOcHjxDmZVGaBGws9vXkcE9D0Z2Q%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANHK%3DJ27pAVHDAXaNAbcF-zJmhfg%3DkvjVptqOF%2BoUoVcGms2jQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: The option to “Launch slave agents via Java Web Start” is missing from new node configuration

[Richard Bywater]

Perhaps it would be an idea to show the item but as disabled and state what
actions are required to get it enabled?

Richard.

On Mon, 15 Aug 2016 at 12:15 Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> So the logic here is to reflect that the TCP agent port has been disabled
> and thus the launcher is not available to you.
>
> On 4 August 2016 at 11:47, Kumar Dp  wrote:
>
>> I'm trying to configure a salve using "Launch slave agents via Java Web
>> Start", but I see that option is not listed in the launch method. I'm using
>> Jenkins 2.14 version.OS: Linux 3.8.13-68.3.4.el6uek.x86_64
>> Please help me to solve the issue
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/21bef93a-67f6-4eb4-887b-ea1bc7d5f6cd%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMzbwTVUYGXuuZ1vx52rcj_G26LjWJkt24KVE%3DC1bJ2t0Q%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMui945xtpCZ-SjuuuUrGvmOcHjxDmZVGaBGws9vXkcE9D0Z2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: The option to “Launch slave agents via Java Web Start” is missing from new node configuration

[Stephen Connolly]

So the logic here is to reflect that the TCP agent port has been disabled
and thus the launcher is not available to you.

On 4 August 2016 at 11:47, Kumar Dp  wrote:

> I'm trying to configure a salve using "Launch slave agents via Java Web
> Start", but I see that option is not listed in the launch method. I'm using
> Jenkins 2.14 version.OS: Linux 3.8.13-68.3.4.el6uek.x86_64
> Please help me to solve the issue
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/21bef93a-67f6-4eb4-887b-ea1bc7d5f6cd%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMzbwTVUYGXuuZ1vx52rcj_G26LjWJkt24KVE%3DC1bJ2t0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Best practices: many distinct jobs vs parameterized jobs

[Daniel Beck]

> On 13.08.2016, at 16:23, w...@anomalizer.net wrote:
> 
> The only way to track it separately in jenkins 1.x is to have one job for 
> each. Jenkins 2.x has a mechanism wherein you have have a single job 
> (pipeline) across the branches and yet, track their statistics separately.

The Pipeline suite of plugins is compatible with 1.x, but not available out of 
the box.

Also, there are one or two plugins that implement a similar "multi branch" 
behavior with freestyle based configuration.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/89E2ACDF-44E0-4D25-BF95-F5FF34EB2D9B%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: What are industry standard ways of managing server logins that Jenkins does for its builds?

[Daniel Beck]

> On 13.08.2016, at 14:46, Kiran  wrote:
> 
>   "Manage credentials" the native Jenkins feature
>   "Credentials Plugin"
>   "SSH Credentials plugin"

These are all basically the same thing.

SSH Credentials Plugin is based on Credentials Plugin and provides the SSH 
credentials types (while IIRC Credentials Plugin only has generic 
username/password).

'Manage Credentials' in the sidebar is provided by the Credentials Plugin.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/C80DA594-DAB3-44F3-BCF1-F9463860612E%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: How can I get Jenkins on Linux to do builds on Windows machines without Active Directory?

[jpd4nt]

Jenkins has a master slave feature, Linux running jenkins is the master - 
Windows doing the build is a slave.

What you need to get working is the connection from the Windows slave to 
the master, since Windows does not really have support for SSH (not sure 
how far the powershell guys got) use the jnlp to get it up and working.

See: 
https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice%28require.NET2.0framework%29

if that does not work, all it really does is run the jnlp at boot which you 
can do vi powershell and scheduler thing in windows.

At the moment you don't need any plugins.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/331fadbd-92ef-477f-af78-69cc9b4fc5ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Post- Commit VisualSVN Server

[Karen Medhat]

Hello All,

Would you please advise on a simple way to notify jenkins to issue a build 
whenever a new change is committed on VisualSVN server. I have added 
the post-commit.bat & post-commit-hook-jenkins.vbs
as advised here 
: 
https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin#SubversionPlugin-Windowsspecificpostcommithook
but it fails 

This is the repository url : https://IBM257-R8FLY1A/svn/jenkins1/ 

Thanks in advance 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4967470f-24b4-4ec9-a869-36831cb37556%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Access-Control-Allow-Origin different for userContent rather than build pages?

[Jonathan Hodgson]

Hi,

I have anartifacts, which are xml logs from MSBuild.

Now in my build description I have a HTML and some javascript which reads 
those files and shows me which architectures and configurations have 
warnings or errors.

That bit works fine, as each build completes, its associated cell in the 
table goes green, yellow or red, and I see the number of errors and 
warnings.

So far so good.

But as well as colouring the cell, and showing the number of 
errors/warnings, the code also and an href to an HTML file in userConten   
with a GET parameter in the URL giving the location of one of the xml log 
which uses javascript and xslt to create a moe complete build log.

I prefer to keep that file separate from the the build so that I can 
improve the rendering of the log over time.

Anyway, that doesn't work.

Note that I've tested the html and javascript in python simpleHTTP server, 
and they work correctly.

But when I'm accessing it from Jenkins I get

SEC7120: Origin http:/:8080 not found in 
Access-Control-Allow-Origin header.

in the console browser (Microsoft Edge, Chrome gives basically the same 
error, but is more verbose).

This despute the fact that I'm trying to read he same xml file, in the same 
way, as succeeded in the javascript in the build page description.

Does anybody have any idea what's going on? And hopefully a 
solution/workaround.

regards

Jon

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9cee443c-0ecc-443b-92be-2b5cf80e3875%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How can I get Jenkins on Linux to do builds on Windows machines without Active Directory?

[Kiran]

I am using Jenkins 1.6.

The Windows *slave*?  Is the target of a Jenkins build a "slave"?  The 
Windows servers are those that will get builds (builds that were initiated 
by Jenkins).

Which plugin?  I tried different plugins.  I am open to using whatever that 
works.  I was thinking of having an "Execute Shell" or "Execute Python" job 
with variables that had credentials.  The credentials would stored using 
the "Manage Credentials" feature of Jenkins. The credentials would be 
for local administrators on the Windows servers.  The method needs to be 
secure (not passed via plaintext over the network).

I know how to install plugins.  The Jenkins server has no internet 
connection.  I get the .hpi file and restart Jenkins services.

If I need to use a plugin, I could use one of these:

  "SSH Credentials plugin"
  "Publish over SSH plugin" 

I'm not sure what will be necessary.  What do you recommend?


On Saturday, August 13, 2016 at 4:50:42 PM UTC-4, jpd4nt wrote:
>
> Which version of jenkins are you using?
> Which plugin a you using to manage the Windows slave?
>
> We use Windows build slaves on AWS with no AD with not problems with the 
> ec2-plugin, before that with v1 of jenkins there was jnlp which made POC 
> easy to get up and running but with v2 thats gone but the modules seem to 
> plug the gap nicely.
>
> The passwords are securely encrypted as this module uses the credentials 
> plugin, so have you got the windows slave plugin installed?
>
> There is a gui in Jenkins that does the plugin installation for you so you 
> should not need to manually download and install listed module. 
>
>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f2c558f6-521a-4ff3-a704-d7f0d6f8d01f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.