Re: Tying upstream/downstream projects execution nodes by name?

[Olexij Tkatchenko]

I forgot to mention, that having that I am able to reboot '"driven" machine 
before actual build. "driver" starts a reboot of "driven" and waits, until 
it is completed.

Am Montag, 22. Juli 2013 16:06:28 UTC+2 schrieb Olexij Tkatchenko:
>
> It worked, thanks! I have 2 nodes - node1 ("driver"), and node12 
> ("driven"). "Driver" executes a downstream project on a node named 
> ${NODE_NAME}2, which is obviously "driven". One can also go further and 
> "tie" node12 to downstream project by setting "*Leave this machine for 
> tied jobs only"*
>
> Am Sonntag, 21. Juli 2013 09:16:36 UTC+2 schrieb Daniel Beck:
>>
>> The combination Parameterized Trigger plugin + NodeLabel Parameter plugin 
>> might work. The environment variable 'NODE_NAME' stores the name of the 
>> node. 
>>
>> On 21.07.2013, at 04:59, Olexij Tkatchenko  
>> wrote: 
>>
>> > How to implement a dynamic selection of a node for downstream project 
>> based on name of the node of upstream project? For example, if the node for 
>> the upstream project is called "node1" then the node for the downstream 
>> project should be called "node11", for "node2" - "node21" and so on. 
>> > 
>> > -- 
>> > 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-use...@googlegroups.com. 
>> > For more options, visit https://groups.google.com/groups/opt_out. 
>> >   
>> >   
>>
>>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [ANN] jenkins-ci.org site outage

[Kohsuke Kawaguchi]

I've fixed this problem now. Sorry for a delay.

On 07/22/2013 03:20 PM, m...@arangamani.net wrote:

I am having the same problem releasing my first plugin.

On Sunday, July 21, 2013 2:06:47 PM UTC-7, Jan Molak wrote:

Hi all,

I started getting a 401 - Unauthorised when trying to deploy my
plugin to
http://maven.jenkins-ci.org:8081/content/repositories/releases/
 a
couple of minutes ago.
I've deployed several times already over the last couple of weeks

(http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/build-monitor-plugin/

)
and my configuration hasn't changed since then - it's an automated job.

Could this be related to the outage you mentioned, Kohsuke?

Best,
Jan

On Sunday, 21 July 2013 18:39:28 UTC+1, R Tyler Croy wrote:


On Wed, 17 Jul 2013, Kohsuke Kawaguchi wrote:

 > The data center that's housing one of our key servers
(63.246.20.93) is
 > going to perform an infrastructure upgrade on July 21st
between 02:00am UTC
 > to 08:00am

UTC>

 > .
 >
 > During this migration, multiple services will be unavailable.
This will
 > impact both users and developers of the project.
 >
 > I collected the details at
 >
https://wiki.jenkins-ci.org/display/JENKINS/Server+Migration+2013+July




This work has been completed and DNS should be updated for
everybody.

If you have any issues please let me know either via #jenkins on
IRC (rtyler)
or on this thread.


Cheers
- R. Tyler Croy
--
 Code: https://github.com/rtyler
  Chatter: https://twitter.com/agentdero

--
You received this message because you are subscribed to the Google
Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.





--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [ANN] jenkins-ci.org site outage

[me]

I am having the same problem releasing my first plugin.

On Sunday, July 21, 2013 2:06:47 PM UTC-7, Jan Molak wrote:
>
> Hi all,
>
> I started getting a 401 - Unauthorised when trying to deploy my plugin to 
> http://maven.jenkins-ci.org:8081/content/repositories/releases/ a couple 
> of minutes ago.
> I've deployed several times already over the last couple of weeks (
> http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/build-monitor-plugin/)
>  
> and my configuration hasn't changed since then - it's an automated job.
>
> Could this be related to the outage you mentioned, Kohsuke?
>
> Best,
> Jan
>
> On Sunday, 21 July 2013 18:39:28 UTC+1, R Tyler Croy wrote:
>>
>>
>> On Wed, 17 Jul 2013, Kohsuke Kawaguchi wrote: 
>>
>> > The data center that's housing one of our key servers (63.246.20.93) is 
>> > going to perform an infrastructure upgrade on July 21st between 02:00am 
>> UTC 
>> > to 08:00am UTC<
>> http://www.timeanddate.com/worldclock/fixedtime.html?msg=Jenkins+server+migration&iso=20130721T02&ah=6>
>>  
>>
>> > . 
>> > 
>> > During this migration, multiple services will be unavailable. This will 
>> > impact both users and developers of the project. 
>> > 
>> > I collected the details at 
>> > https://wiki.jenkins-ci.org/display/JENKINS/Server+Migration+2013+July 
>>
>>
>> This work has been completed and DNS should be updated for everybody. 
>>
>> If you have any issues please let me know either via #jenkins on IRC 
>> (rtyler) 
>> or on this thread. 
>>
>>
>> Cheers 
>> - R. Tyler Croy 
>> -- 
>> Code: https://github.com/rtyler 
>>  Chatter: https://twitter.com/agentdero 
>>
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Looking for suggestions on how to gather more information about an error on the Build History & buildTimeTrend pages?

[Kevin Pease]

Good afternoon,

For the past couple days, I've been seeing an odd issue when I try to load 
the 'Build History' page in Jenkins, and I'm trying to understand what's 
happening, and I'm not sure where else to look.  The issue was happening 
with 1.521, and I upgraded to latest (1.523 + all plugins updated) this 
morning, and am still seeing the issue.

When I load the Build History page (in Chrome), I get 2 popup dialogs, 
which simply read:

 Title Bar:  *The page at https://server.name.com/ says:*
 Content:   *SyntaxError:  Unexpected token )*
*
*
The dialogs appear one after another, and provide no other clues.  The 
Build History page seems to load okay, but every time the page refreshes, 
these 2 dialogs pop up again.

If I turn on the Javascript console in Chrome, I see the following error 
messages show up at the same time the dialogs pop up:

*GET   https://server.name.com/jenkins/view/All/__history__.html?0 404 (Not 
Found)   
  simile-ajax-bundle.js:1980*
*POST https://server.name.com/jenkins/view/All/timeline/data/  

  prototype.js:1585
POST https://server.name.com/jenkins/view/All/timeline/data/
  
  prototype.js:1585*


The system was working fine for some time, so I don't think it's my 
Apache/Tomcat/SSL Proxy configuration, though if it's relevant I can share 
that information.

I'm fairly certain that I have a corrupted Job or Build file somewhere, but 
I'm stuck at trying to figure out which job/build/etc. is causing this 
issue - is there anything else I can do to turn on some additional 
logging/data collection options to try and figure out what the underlying 
issue is?  I'm in the process of building a prototype system for the dev 
organization I support right now, so if I need to, I can start deleting & 
recreating jobs to try and figure out what's causing this, but I'd prefer 
not to if it's avoidable.

This same issue also happens on the buildTimeTrend page for individual job 
build histories as well.

Any suggestions as to how I can get more data on this would be very welcome.

Thanks,

Kevin Pease

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Including changelog

[Maureen Barger]

Never mind, problem lies behind the keyboard. Let me get back to you
after I update that plugin (blush)

On Mon, Jul 22, 2013 at 1:58 PM, Maureen Barger  wrote:
> On Mon, Jul 22, 2013 at 1:18 PM, Daniel Beck  wrote:
>> check to store the email in the workspace ("Save Generated E-mail to 
>> Workspace").
>
> Thanks, but I am just not seeing this checkbox!

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Source safe configuration

[Eric Pyle]

If the folder where Source safe resides is on a network drive, make sure 
the user account running Jenkins has access to that folder. You don't 
say whether you are on Linux or Windows, and when the error comes up. Is 
it when running a job or when trying to start Jenkins? You should also 
specify what version of Jenkins you are running, as well as the version 
of Source Safe plugin.


Eric

On 7/22/2013 1:22 PM, Nateshkumar NS wrote:

Please advice.

Thanks.

On Friday, July 19, 2013 5:01:40 PM UTC-4, Nateshkumar NS wrote:

I am new to Jenkins.
I get the error while
srcsafe.ini doesn't exist. Configuration error.

Tried giving IP address, mapped drive path, made the folder where
srssafe.ini resides as shareable.
Nothing works.
Please advice.

Thanks.

--
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.

For more options, visit https://groups.google.com/groups/opt_out.




--
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.
For more options, visit https://groups.google.com/groups/opt_out.

RE: Triggered job - run on same machine?

[Bob Bick]

Thanks Rob... I realized that they would run in two different subdirectories, 
and that is why I was passing the subdirectory of the upstream job to the 
downstream job.

-Original Message-
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mandeville, Rob
Sent: Monday, July 22, 2013 9:42 AM
To: 'jenkinsci-users@googlegroups.com'
Subject: RE: Triggered job - run on same machine?

There is no reason that the downstream job will run on the same node as the 
upstream one.  Even if it happened to do so, they would be in two different 
subdirectories of the workspace.

You can use the Copy Artifact plugin, or you can make the builders of the 
downstream job a build step in the upstream job, effectively turning it into 
one job.

--Rob

-Original Message-
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Bob Bick
Sent: Monday, July 22, 2013 8:18 AM
To: 'jenkinsci-users@googlegroups.com'
Subject: Triggered job - run on same machine?

Hi,

I am using the Jenkins Parameterized Trigger Plugin to trigger a downstream 
job. The downstream job leverages artifacts from the upstream job; hence, I am 
passing the workspace of the upstream job to the downstream job.

Q. Is it safe to do that? Will it always run on the same node? Or, should you 
always use the Copy Artifact plugin?

Thanks,

Bob

*** *** ***
This message contains information which may be confidential and privileged. 
Unless you are the addressee (or authorized to receive for the addressee), you 
may not use, copy or disclose to anyone the message or any information 
contained in the message. If you have received the message in error,  please 
advise the sender by reply e-mail and delete the message.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.


The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.



*** *** ***
This message contains information which may be confidential and privileged. 
Unless you are the addressee (or authorized to receive for the addressee), you 
may not use, copy or disclose to anyone the message or any information 
contained in the message. If you have received the message in error,  please 
advise the sender by reply e-mail and delete the message.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Including changelog

[Daniel Beck]

You could use emailext to record changes in the actual build:
1. Create an email with the changes on build success, and check to store the 
email in the workspace ("Save Generated E-mail to Workspace"). Not sure whether 
you need actual recipients if you check that option.
2. Copy that with the build results to the upload job, and use the ${FILE} 
macro in the upload job's emailext.

Alternatively, you can probably use the Any Build Step plugin to add a shell 
script builder to your job as a post-build action (since you mentioned that).

On 22.07.2013, at 17:08, Maureen Barger  wrote:

> We have a maven build of several artifacts. These artifacts are FTP'd
> nightly at 9pm as a separate job from the build. We would like to
> include the changes since last build with our upload.
> 
> Issues:
> Since it's a maven job, I can't execute a shell command at build.
> I've installed Changes Since Last Success Plugin but I am not seeing
> it in the build menu of any new job I create, and since this is a
> maven job, I don't have the build option anyway.
> I have the mail-ext plugin installed and it does great to send out the
> email to interested parties when the FTP upload is complete. And it
> even has a changelog feature but since the build job (which would
> actually contain the changes) and the FTP job are separate, the
> changelog feature is meaningless here.
> 
> Ideally I would like to send a changelog since last upload but a
> changelog of that release, just added on to the file as we go, would
> suffice as well.
> 
> Any suggestions?
> 
> -- 
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 
> 

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Including changelog

[Maureen Barger]

On Mon, Jul 22, 2013 at 1:18 PM, Daniel Beck  wrote:
> check to store the email in the workspace ("Save Generated E-mail to 
> Workspace").

Thanks, but I am just not seeing this checkbox!

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Modifying a builds parameters in a system Groovy script

[kormbrek]

Following Reuben's comments I came up a util function. Posting here so 
other people can see a working example.

import hudson.model.*

// sets build parameters based on the given map
// only supports StringParameterValue
def setBuildParameters(map) {
def npl = new ArrayList()
for (e in map) {
npl.add(new StringParameterValue(e.key.toString(), 
e.value.toString()))
}
def newPa = null
def oldPa = build.getAction(ParametersAction.class)
if (oldPa != null) {
build.actions.remove(oldPa)
newPa = oldPa.createUpdated(npl)
} else {
newPa = new ParametersAction(npl)
}
build.actions.add(newPa)
}

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Including changelog

[Maureen Barger]

We have a maven build of several artifacts. These artifacts are FTP'd
nightly at 9pm as a separate job from the build. We would like to
include the changes since last build with our upload.

Issues:
Since it's a maven job, I can't execute a shell command at build.
I've installed Changes Since Last Success Plugin but I am not seeing
it in the build menu of any new job I create, and since this is a
maven job, I don't have the build option anyway.
I have the mail-ext plugin installed and it does great to send out the
email to interested parties when the FTP upload is complete. And it
even has a changelog feature but since the build job (which would
actually contain the changes) and the FTP job are separate, the
changelog feature is meaningless here.

Ideally I would like to send a changelog since last upload but a
changelog of that release, just added on to the file as we go, would
suffice as well.

Any suggestions?

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Source safe configuration

[Nateshkumar NS]

Please advice.

Thanks.

On Friday, July 19, 2013 5:01:40 PM UTC-4, Nateshkumar NS wrote:
>
> I am new to Jenkins. 
> I get the error while 
> srcsafe.ini doesn't exist. Configuration error. 
>
> Tried giving IP address, mapped drive path, made the folder where 
> srssafe.ini resides as shareable. 
> Nothing works. 
> Please advice. 
>
> Thanks.
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Tying upstream/downstream projects execution nodes by name?

[Olexij Tkatchenko]

It worked, thanks! I have 2 nodes - node1 ("driver"), and node12 
("driven"). "Driver" executes a downstream project on a node named 
${NODE_NAME}2, which is obviously "driven". One can also go further and 
"tie" node12 to downstream project by setting "*Leave this machine for tied 
jobs only"*

Am Sonntag, 21. Juli 2013 09:16:36 UTC+2 schrieb Daniel Beck:
>
> The combination Parameterized Trigger plugin + NodeLabel Parameter plugin 
> might work. The environment variable 'NODE_NAME' stores the name of the 
> node. 
>
> On 21.07.2013, at 04:59, Olexij Tkatchenko 
> > 
> wrote: 
>
> > How to implement a dynamic selection of a node for downstream project 
> based on name of the node of upstream project? For example, if the node for 
> the upstream project is called "node1" then the node for the downstream 
> project should be called "node11", for "node2" - "node21" and so on. 
> > 
> > -- 
> > 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-use...@googlegroups.com . 
> > For more options, visit https://groups.google.com/groups/opt_out. 
> >   
> >   
>
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

RE: Triggered job - run on same machine?

[Mandeville, Rob]

There is no reason that the downstream job will run on the same node as the 
upstream one.  Even if it happened to do so, they would be in two different 
subdirectories of the workspace.

You can use the Copy Artifact plugin, or you can make the builders of the 
downstream job a build step in the upstream job, effectively turning it into 
one job.

--Rob

-Original Message-
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Bob Bick
Sent: Monday, July 22, 2013 8:18 AM
To: 'jenkinsci-users@googlegroups.com'
Subject: Triggered job - run on same machine?

Hi,

I am using the Jenkins Parameterized Trigger Plugin to trigger a downstream 
job. The downstream job leverages artifacts from the upstream job; hence, I am 
passing the workspace of the upstream job to the downstream job.

Q. Is it safe to do that? Will it always run on the same node? Or, should you 
always use the Copy Artifact plugin?

Thanks,

Bob

*** *** ***
This message contains information which may be confidential and privileged. 
Unless you are the addressee (or authorized to receive for the addressee), you 
may not use, copy or disclose to anyone the message or any information 
contained in the message. If you have received the message in error,  please 
advise the sender by reply e-mail and delete the message.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.


The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Template Project plugin

[Maureen Barger]

Hi - I just wanted to follow up that Daniel Beck's solution worked
perfectly for me. Now the SCM team only has to define the release
string in one location. Other parameters include some host names and
other paths that were repeated in other jobs.

I have one job that we run when a release rolls over and set these as
a file in the file system (not as an artifact).
Then the other jobs simply have an extra step "Inject environment
variables to the build process" that point to the properties file on
disk.

Works great! Thank you!

On Wed, Jul 10, 2013 at 2:08 PM, syl20bnr  wrote:
> You can also use the build parameterized trigger plugin you already use to
> read from the property file using "Parameters from properties file". The
> plus sides are that build parameters are recorded in build histories and the
> values will be set before that the SCM step occurs.
>
> Cheers,
> syl20bnr
>
> Le mercredi 10 juillet 2013 06:16:19 UTC-4, MoBarger a écrit :
>>
>> I like it! I was thinking about a properties file but never thought of
>> creating it as an artifact! Thanks for the idea!
>>
>> On Wed, Jul 10, 2013 at 6:09 AM, Daniel Beck  wrote:
>> > In a similar situation I defined one job ("Configuration") that created
>> > a .properties file with the relevant options based on job paraemters and
>> > archived it as artifact.
>> >
>> > The other jobs then used the Copy Artifact plugin to get the file ("Copy
>> > from last successful build" uses the current option set), and a build step
>> > defined in Env-Inject to inject those options into the environment for
>> > subsequent build steps. For more flexibility, use a build selector
>> > parameter, or specify a build number as string parameter and copy artifacts
>> > from a 'specific build'.
>> >
>> > On 10.07.2013, at 11:13, Maureen Barger  wrote:
>> >
>> >> Right, thanks, we do use that and it works well. But this works best
>> >> when one job triggers another.
>> >> In my case the processes are fired off at different times. The same
>> >> parameters have to be set on each top job which seems like too many
>> >> moving parts to me.
>> >> Ideally I could set up a job which only defines the release number and
>> >> a couple other parameters that would be referenced by each kickoff of
>> >> the process (ie build, deploy, test, package).
>> >>
>> >> On Tue, Jul 9, 2013 at 9:52 PM, syl20bnr  wrote:
>> >>> You should be able to do this with the Parameterized Build plugin
>> >>> (https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build). At 
>> >>> work
>> >>> we use Perforce and we use this plugin to pass the variable 
>> >>> P4_CHANGELIST to
>> >>> downstream job (with the perforce plugin configured with P4_CHANGELIST 
>> >>> as a
>> >>> label). It works fine.
>> >>>
>> >>> Now you write that you have several build parameters. Depending on how
>> >>> you use them it may lead to mess your build history with the same job 
>> >>> called
>> >>> with different parameters.
>> >>> You may want to look at Job Generation plugins like JobCopy Builder,
>> >>> Job DSL and Job Generator. I'm the author of the last one. :-)
>> >>>
>> >>> Cheers,
>> >>> syl20bnr
>> >>>
>> >>> --
>> >>> 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-use...@googlegroups.com.
>> >>> For more options, visit https://groups.google.com/groups/opt_out.
>> >>>
>> >>>
>> >>
>> >> --
>> >> 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-use...@googlegroups.com.
>> >> For more options, visit https://groups.google.com/groups/opt_out.
>> >>
>> >>
>> >>
>> >
>> > --
>> > 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-use...@googlegroups.com.
>> > For more options, visit https://groups.google.com/groups/opt_out.
>> >
>> >
>
> --
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Triggered job - run on same machine?

[Bob Bick]

Hi,

I am using the Jenkins Parameterized Trigger Plugin to trigger a downstream 
job. The downstream job leverages artifacts from the upstream job; hence, I am 
passing the workspace of the upstream job to the downstream job.

Q. Is it safe to do that? Will it always run on the same node? Or, should you 
always use the Copy Artifact plugin?

Thanks,

Bob

*** *** ***
This message contains information which may be confidential and privileged. 
Unless you are the addressee (or authorized to receive for the addressee), you 
may not use, copy or disclose to anyone the message or any information 
contained in the message. If you have received the message in error,  please 
advise the sender by reply e-mail and delete the message.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

AW: Access Jenkins Parameter in job

[Steffen Breitbach]

Hi Gaurang!

> Is there any way i can access the jenkins parameter inside the job. ? 

What is "the jenkins parameter"?

Regards
  Steffen

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Access Jenkins Parameter in job

[Gaurang shah]

Hi Guys, 

Is there any way i can access the jenkins parameter inside the job. ? 

Gaurang Shah

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Readonly job parameters

[Daniel Beck]

An actual use case for this might be helpful. Right now, this looks a lot like 
an XY problem [1].

Also, a possible solution is a Choice parameter with only one value to select. 
But note that e.g. Parameterized Trigger will just override this when you 
specify a different value there, so it's on the UI only.

1: http://www.perlmonks.org/?node_id=542341

On 21.07.2013, at 22:53, Thomas Fields  wrote:

> >>No, that I am aware of. I've been kind of thinking about something similar
> but more of like a set of variables that can be defined with the job, and
> then referenced in multiple places within the job configuration.
> Yeah, something like this would be perfect for my needs. 
> 
> Surely it's not too difficult to add a new "read only string parameter" to 
> the parameter options in the job description then display it but obviously 
> don't let the user edit it. Did you enter this in Jira already?
> 
> Cheers
> Tom
> 
> -- 
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

test doesn't fail on exception

[Gaurang shah]

Hi Guys, 

I have configured jenkins with pytest and webdriver. It's running and 
launching test fine however the only problem is test doesn't fail even 
though it has encountered an exception. 

is there any setting or plugin require for that. 


Gaurang shah

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Panic! Jenkins fails building Maven project, but Maven on the same slave succeeds?!

[Markus KARG]

Now it gets even more weird: I just noticed that when I do "mvn deploy" on 
the parent project, then Jenkins will succeed. This is stange, because the 
local repo already contained that artifact -- otherwise the local test 
using "mvn test" of the child project would have failed, too. This really 
looks as if the Maven integration in Jenkins has a rather strange bug...!

Am Montag, 22. Juli 2013 10:16:46 UTC+2 schrieb Markus KARG:
>
> Dear Jenkins Community, please help me before I drive nuts!
>
> Jenkins fails building one of my projects since I released another version 
> of its Maven parent POM...:
>
> [ERROR] The build could not read 1 project -> [Help 1][ERROR]   [ERROR]   The 
> project ... (C:\.jenkins\workspace\...\pom.xml) has 1 error[ERROR] 
> Non-resolvable parent POM: Could not find artifact ... and 
> 'parent.relativePath' points at wrong local POM @ line 8, column 10 -> [Help 
> 2][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven 
> with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full 
> debug logging.[ERROR] [ERROR] For more information about the errors and 
> possible solutions, please read the following articles:[ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException[ERROR]
>  [Help 2] 
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
>
>
> But now comes the strange thing: I log in to exactly that slave, and can 
> *successfully *build *using exactly the same tool chain* Jenkins provided on 
> the slave...
>
> *
> *
>
> *>SET JAVA_HOME=C:\.jenkins\tools\hudson.model.JDK\Java_1.7.0*
>
> *>SET MAVEN_HOME=C:\.jenkins\tools\hudson.tasks.Maven_MavenInstallation*
>
> *>%MAVEN_HOME%\Maven_3.0.4\bin\mvn test*
>
> ...which says "BUILD SUCCESS"!
>
>
> So there must be something wrong with Jenkins 1.514's Maven integration... :-(
>
>
> What can I do? I am totally stuck because I have to release this project 
> today...
>
>
> Thanks!
>
> -Markus
>
>
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: strange heap space

[Raouf Abdelhamid]

Many thanks ! that solved my problem.

I was actually using the default HTTP wagon, so i moved to DAV wagon and
now everythings is working fine.


Thanks to everyone for your help.

Regards,
Raouf.


2013/7/19 Vincent Latombe 

> Hi,
>
> See [1] for a possible workaround (this is the one I use). Basically
> when using maven 3, you just have to prefix your deployment url with
> dav: (ex. dav:http://yourmavenserver). It will use the dav wagon
> instead of the default http one, which has the bad habbit of loading
> the full file in memory before sending it away.
>
> HTH,
>
> Vincent
>
> |1]
> http://maven.40175.n5.nabble.com/Heap-overflow-in-deploy-deploy-td3211324.html
> Vincent
>
>
> 2013/7/19 Raouf Abdelhamid :
> > Okay thanks guys, i'll check the activity of maven-deploy and give you
> some
> > feedback
> >
> >
> > 2013/7/19 Daniel Beck 
> >>
> >> IIRC a few years ago I experienced an issue with very large artifacts
> >> being uploaded to an artifact repository. maven-deploy-plugin couldn't
> >> handle files larger than one third of the available heap space.
> >>
> >> On 19.07.2013, at 12:09, Raouf  wrote:
> >>
> >> > Hi there,
> >> >
> >> > I'm getting a java heap space that i can't really explain. i tried to
> >> > increase the memory allocated to jenkins, but that doesn't change a
> thing
> >> >
> >> > The most strange thing, is that i configured jenkins to not launch
> sonar
> >> > analysis if the build fails, but sonar analysis is launched anyway,
> goes
> >> > sucessful, and then the build is red !
> >> >
> >> > I even tryied to montir the execution of this build with visual VM
> >> > remotely connected to jenkins, but didn't see any heap space error at
> any
> >> > moment.
> >> >
> >> > here's the corresponding log
> >> >
> >> > Uploading:
> >> >
> http://server/archiva/repository/snapshot/project-SNAPSHOT/project-SNAPSHOT-bin.tar.gz
> >> >
> >> > [JENKINS] Archiving /basepath/hudson/workspace/
> >> > project/package/pom.xml to
> >> >
> /basepath/hudson/jobs/project/modules/package$module/builds/2013-07-18_14-08-50/archive/package/module/version-SNAPSHOT/module-version-
> >> > SNAPSHOT.pom
> >> > [JENKINS] Archiving /basepath/hudson/workspace/
> >> > project/package/targetproject-version-SNAPSHOT.jar to
> >> >
> /basepath/hudson/jobs/project/modules/package$module/builds/2013-07-18_14-08-50/archive/package/module/version-SNAPSHOT/project-version-
> >> > SNAPSHOT.jar
> >> > [JENKINS] Archiving /basepath/hudson/workspace/
> >> > project/package/target/project-version-SNAPSHOT-bin.tar.gz to
> >> >
> /basepath/hudson/jobs/project/modules/package$module/builds/2013-07-18_14-08-50/archive/package/module/version-SNAPSHOT/project-version-
> >> > SNAPSHOT-bin.tar.gz
> >> > [INFO] --
> >> > --
> >> > 
> >> >
> >> > [ERROR] FATAL ERROR
> >> >
> >> > [INFO] 
> >> > 
> >> > [INFO] Java heap space
> >> > [INFO] --
> >> > --
> >> > 
> >> > [INFO] Trace
> >> > java.lang.OutOfMemoryError: Java heap space
> >> >   at java.util.Arrays.copyOf(
> >> > Arrays.java:2786)
> >> >   at java.io.ByteArrayOutputStream.
> >> > write(ByteArrayOutputStream.
> >> > java:94)
> >> >   at sun.net.www.http.
> >> > PosterOutputStream.write(
> >> > PosterOutputStream.java:61)
> >> >   at org.apache.maven.wagon.
> >> > AbstractWagon.transfer(
> >> > AbstractWagon.java:338)
> >> >   at org.apache.maven.wagon.
> >> > AbstractWagon.transfer(
> >> > AbstractWagon.java:305)
> >> >   at org.apache.maven.wagon.
> >> > AbstractWagon.transfer(
> >> > AbstractWagon.java:267)
> >> >   at org.apache.maven.wagon.
> >> > AbstractWagon.putTransfer(
> >> > AbstractWagon.java:238)
> >> >   at org.apache.maven.wagon.
> >> > StreamWagon.put(StreamWagon.
> >> > java:143)
> >> >   at org.apache.maven.wagon.
> >> > providers.http.LightweightHttpWagon.put(
> >> > LightweightHttpWagon.java:148)
> >> >   at org.apache.maven.artifact.
> >> > manager.DefaultWagonManager.putRemoteFile(
> >> > DefaultWagonManager.java:244)
> >> >   at org.apache.maven.artifact.
> >> > manager.DefaultWagonManager.putArtifact(
> >> > DefaultWagonManager.java:160)
> >> >   at org.apache.maven.artifact.
> >> > deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:
> >> > 80)
> >> >   at org.apache.maven.plugin.
> >> > deploy.DeployMojo.execute(
> >> > DeployMojo.java:169)
> >> >   at org.apache.maven.plugin.
> >> > DefaultPluginManager.executeMojo(
> >> > DefaultPluginManager.java:451)
> >> >   at hudson.maven.agent.
> >> > PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:
> >> > 182)
> >> >   at org.apache.maven.lifecycle.
> >> > DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
> >> > 558)
> >> >   at org.apache.maven.lifecycle.
> >> >
> >> >
> DefaultLifecycleEx

Panic! Jenkins fails building Maven project, but Maven on the same slave succeeds?!

[Markus KARG]

Dear Jenkins Community, please help me before I drive nuts!

Jenkins fails building one of my projects since I released another version 
of its Maven parent POM...:

[ERROR] The build could not read 1 project -> [Help 1][ERROR]   [ERROR]   The 
project ... (C:\.jenkins\workspace\...\pom.xml) has 1 error[ERROR] 
Non-resolvable parent POM: Could not find artifact ... and 
'parent.relativePath' points at wrong local POM @ line 8, column 10 -> [Help 
2][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug 
logging.[ERROR] [ERROR] For more information about the errors and possible 
solutions, please read the following articles:[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException[ERROR]
 [Help 2] 
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException


But now comes the strange thing: I log in to exactly that slave, and can 
*successfully *build *using exactly the same tool chain* Jenkins provided on 
the slave...

*
*

*>SET JAVA_HOME=C:\.jenkins\tools\hudson.model.JDK\Java_1.7.0*

*>SET MAVEN_HOME=C:\.jenkins\tools\hudson.tasks.Maven_MavenInstallation*

*>%MAVEN_HOME%\Maven_3.0.4\bin\mvn test*

...which says "BUILD SUCCESS"!


So there must be something wrong with Jenkins 1.514's Maven integration... :-(


What can I do? I am totally stuck because I have to release this project 
today...


Thanks!

-Markus


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Pipeline plugin]Is it possible to select a parameterized job as the initial job

[lulli]

Hi Team,

 

I installed the build pipeline plugin 1.3.5 but I found if I select a 
parameterized job as the initial job, the run button will not work.

The job will not run and the page will not updated.

So is it possible to do this? Or the initial job must be a 
non-parameterized job?

 

Thanks & Regards

Lavar Li

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.