Re: overwrite an environment variable

[Jochen Wiedmann]

How about writing the value to a temporary file instead? A shell
script could use the file later on (in another stage) to set the
environment variable.

On Wed, Apr 14, 2021 at 9:01 PM webde...@gmail.com
 wrote:
>
> hey, all!
>
> Here's what I would like to do:
>
> 1. in the pipeline itself, create an environment variable.
> 2. pass that environment variable to a job
> 3. that job will overwrite the environment variable's value at the top level
> 4. a later job will use this new value within its execution.
>
> something like:
>
> pipeline {
> agent {
> label 'Computer'
> }
>
> environment {
> 1.pipelineVariable = "15"3. (after the changeVariableValue job, 
> variable value is now 7)
> }
>
> stages {
> stage('change variable value') {
> steps {
> script {
> 2build job: changeVariableValue
> parameter: [[$class: 'StringParameterValue', name: 
> 'PipelineVariable', """${pipelineVariable}"""]]
>}
> }
> }
> stage('new variable value') {
> steps {
> script {
> 4build job: newVariableValue  
>   
>   parameter: [[$class: 'StringParameterValue', name: 'PipelineVariable', 
> """${pipelineVariable}"""]]
>}
> }
> }
> }
> }
>
> The jobs are written in Powershell.
>
> Is there a way to do this?
>
>
> --
> 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/13fe1896-18d5-4566-99b6-5b1044b7934cn%40googlegroups.com.



-- 

Look, that's why there's rules, understand? So that you think before
you break 'em.

-- (Terry Pratchett, Thief of Time)

-- 
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/CAF8HOZJF0xeVXFagZwxDQvgrWroi%3DC%2BsQXhDkQ5KJmnDcHWteQ%40mail.gmail.com.

Re: EC2 provision: A problem occurred while processing the request

[Amedee Van Gasse]

I got it sorted with help on Stack 
Overflow: 
https://stackoverflow.com/questions/67079854/jenkins-ec2-plugin-instances-not-starting/67104641#67104641
Missing subnet.

On Wednesday, April 14, 2021 at 10:05:08 AM UTC+2 Amedee Van Gasse wrote:

> When provisioning a configured EC2 cloud (in the nodes page in Jenkins 
> when you hit the provision via  button), I get this error:
>
>  Oops!
> A problem occurred while processing the request.
>
> Logging ID=8ead3651-3809-4a47-984c-e0e494c705bb
>

-- 
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/bea70625-e2c3-49d6-a0cc-51f3543fffb7n%40googlegroups.com.

Jenkins 2.263.2: "No Proxy Host" not working

['Christoph Leiter' via Jenkins Users]

Hello *,

my first post here ;-)
We're emigrating from an old Jenkins 1.642.2 to 2.263.2.
The new jenkins was installed and configured from scratch, so no config 
files or anything else was copied from the old Jenkins to the new one.
"HTTP Proxy Configuration" was done with the same values as on the old one:


*Server: Port: 1234*
*Password: secured*
*No Proxy Host: *.domain.net*

A buildjobs uses a "curl" and connects to a host *foo.domain.net*
This job run on our old Jenkins.
running on the new Jenkins we run into proxy errors. Checking the 
environment variables before executing the *curl *showed, that *http_proxy *was 
set (whereas it isn't set in the old Jenkins).
The Jenkins-User's environment hasn't set *http_proxy*.

I found some old issues, which were fixed. Any hints here?
Do we have a wrong understanding of this setting? Bug or feature?

Thanks and regards,
Chris

-- 
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/e20d46a0-2c2a-48d0-a9f5-a97f92fdbbdan%40googlegroups.com.

Re: Can I send cppcheck results through slack in a jenkins pipeline?

[jesus fernandez]

Thanks it is working now, I am also wondering what is the tool-id when 
trying to access the details of the analysis result, explained 
here 
https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#summary-of-the-analysis-result
 
I cannot find other reference to what tool id is. I guess each tool (in my 
case cppcheck) has an id for the plugin what I cannot finde which ID 
correspond to each tool

El miércoles, 14 de abril de 2021 a las 20:57:21 UTC+2, 
ullrich...@gmail.com escribió:

> You must wrap it into tm: see 
> https://github.com/jenkinsci/warnings-ng-plugin/blob/master/ui-tests/src/test/java/io/jenkins/plugins/analysis/warnings/SmokeTests.java#L99
>
>
> Am 13.04.2021 um 16:17 schrieb jesus fernandez :
>
> How can I access those token macros? (sorry if this is a silly question) I 
> have never used them before, I tried to print the value with ```println 
> ${ANALYSIS_ISSUES_COUNT, tool="cppcheck", type="NEW"}``` but I get an 
> unexpected token error
>
> El viernes, 9 de abril de 2021 a las 14:03:39 UTC+2, ullrich...@gmail.com 
> escribió:
>
>>
>> https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#token-macro-support
>>
>> Am 09.04.2021 um 13:59 schrieb jesus fernandez :
>>
>> Thanks for replying, any documentation or link to guide me in the right 
>> direction on how to do it? I am quite Junior and have been learning Jenkins 
>> on my own
>>
>> El viernes, 9 de abril de 2021 a las 13:46:48 UTC+2, ullrich...@gmail.com 
>> escribió:
>>
>>> Exporting results from one plugin into another plugin is definitely 
>>> possible. You typically have two steps:
>>> 1) Export the data from a producer plugin
>>> a) using Tokens
>>> b) using API methods of the plugin
>>> 2) Import the data (or reformat and aggregate it) into a consumer plugin
>>>
>>> For step 1 I can say this works for the warnings plugin, it can export 
>>> the results of CppCheck either into tokens or into objects (that you can 
>>> process using your pipeline). 
>>>
>>> I have no idea if the slack plugin is capable of doing step 2 though, 
>>> but I would assume that it works in that way...
>>>
>>> Am 09.04.2021 um 08:39 schrieb jesus fernandez :
>>>
>>> I just started using cppcheck, and I was wondering if there is any way 
>>> to access to the report values (for instance number of total errors) and 
>>> send it to slack. I have been searching in the documentation and here in SO 
>>> but I have found nothing, as I just have been using Jenkins for a couple of 
>>> months ( I am a junior dev) I was wondering if somebody know if this is 
>>> possible and could drive me in the right direction.
>>>
>>> -- 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/d3aee90e-5331-480f-84d7-4df7c3ebcf6fn%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>>
>>>
>> -- 
>> 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.
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/abdfdbec-e2cf-4f69-a089-1cb93dcef30en%40googlegroups.com
>>  
>> 
>> .
>>
>>
>>
> -- 
> 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.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/c5ba204c-fa9f-4f6c-800f-69dba9680f87n%40googlegroups.com
>  
> 
> .
>
>
>

-- 
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/cc21e77e-8e16-4cac-9f6d-a79723d9b6c2n%40googlegroups.com.

Re: how to access all classes and methods of a plugin in jenkins pipeline?

[jesus fernandez]

Yes I will do so


El miércoles, 14 de abril de 2021 a las 21:00:34 UTC+2, 
ullrich...@gmail.com escribió:

> Can you please file a bug report for the warnings plugin, it seems 
> something broken in my build...
>
> Am 14.04.2021 um 18:55 schrieb jesus fernandez :
>
> yes all the other plugins I have checked so far have a woeking javadoc
>
> El mié., 14 abr. 2021 18:20, Ullrich Hafner  
> escribió:
>
>> I publish one, but never looked at the results. Does that work for other 
>> plugins?
>>
>> Am 13.04.2021 um 13:32 schrieb jesus fernandez :
>>
>> is there a javadoc for warnings-ng plugin? or just the github? I get a 
>> 404 when accesing the warnings-ng javadoc
>>
>> El lunes, 12 de abril de 2021 a las 14:28:33 UTC+2, ullrich...@gmail.com 
>> escribió:
>>
>>> In the source code in GitHub?
>>>
>>> You can also look for methods annotated with ExportedBean.
>>>
>>> Am 12.04.2021 um 10:16 schrieb jesus fernandez :
>>>
>>>
>>> where can I see that? in the javadoc I do not see any method with that 
>>> annotation, thoug I could use the getResults() with no problems
>>> El domingo, 11 de abril de 2021 a las 21:43:06 UTC+2, ullrich...@
>>> gmail.com escribió:
>>>
 Due to security considerations only methods marked with @Whitelisted 
 are accessible in Groovy scripts. Does your getter have such an annotation?

 Am 11.04.2021 um 19:02 schrieb jesus fernandez >>> >:

 I am a junior dev trying to lear about Jenkins, I have been learning on 
 my own for a couple of months. Currently I have a pipeline (just for 
 learning purposes) which runs static analysis on a folder, and then 
 publish 
 it, I have been able to send a report through email using jelly templates, 
 from there I realized it is posbile to instantiate the classes of a plugin 
 to use its methods so I went to the cppcheck javadoc here 
 https://javadoc.jenkins.io/plugin/cppcheck/ and did some trial and 
 error so I can get some values of my report and then do something else 
 with 
 them something, so I had something like this in my pipeline:
 ```
 pipeline {
 agent any

 stages {
   stage('analysis') {
 steps {
   script{
 bat'cppcheck "E:/My_project/Source/" --xml --xml-version=2 . 2> 
 cppcheck.xml'
   }
}
 }
 stage('Test'){
   steps {
 script {
   publishCppcheck pattern:'cppcheck.xml'
   for (action in currentBuild.rawBuild.getActions()) {
 def name = action.getClass().getName()
 if (name == 
 'org.jenkinsci.plugins.cppcheck.CppcheckBuildAction') {
def cppcheckaction = action
def totalErrors = 
 cppcheckaction.getResult().report.getNumberTotal()
println totalErrors
def warnings = 
 cppcheckaction.getResult().statistics.getNumberWarningSeverity()
println warnings
   }
 }
   } 
 }
 }
 }

 }
 ```
 which output is:
 ```
 [Pipeline] echo
 102
 [Pipeline] echo
 4
 ```

 My logic (wrongly) tells me that if I can access to the report and 
 statistics classes like that and uses their methods getNumberTotal() and 
 getNumberWarningSeverity() respectively, therefore I should be able to 
 also 
 access the ```DiffState``` class in the same way and use the 
 ```valueOf()``` method to get an enum of the new errors. But adding this 
 to 
 my pipeline:
 ```
 def nueva = cppcheckaction.getResult().diffState.valueOf(NEW)
 println nueva
 ```
 Gives me an error:
 ```
 org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: 
 No such field found: field 
 org.jenkinsci.plugins.cppcheck.CppcheckBuildAction diffState
 at 
 org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.unclassifiedField(
 SandboxInterceptor.java:425 )
 at 
 org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(
 SandboxInterceptor.java:409 )
 ...
 ```

 -- 
 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.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-users/ca24b1f9-b0a8-4e81-8101-0b25f8267602n%40googlegroups.com
  
 
 .



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

Re: Git Plugin Checkout From Branch With Tag

[Eric Fetzer]

So when you turn a tag into a release, does it then act more like a label,
or is it still just a set of changed files?

On Wed, Apr 14, 2021 at 12:48 PM Mark Waite 
wrote:

>
>
> On Wed, Apr 14, 2021 at 12:16 PM eric.fetzer 
> wrote:
>
>> Thamks Mark!  So how would I go about checking out a branch based on a
>> point in time (a label in most systems)?  Is there a way to snap a label
>> and then check out based on that label or are we resigned to only deal in
>> tip revisions?
>>
>>
> You can checkout a point in time by checking out a specific SHA-1 hash
> that is the most recent commit before that point in time.  See
> https://stackoverflow.com/questions/6990484/how-to-checkout-in-git-by-date
> .
>
>
>>
>>
>> Sent from my T-Mobile 4G LTE Device
>>
>>
>>  Original message 
>> From: Mark Waite 
>> Date: 4/14/21 1:44 PM (GMT-05:00)
>> To: Jenkins Users 
>> Subject: Re: Git Plugin Checkout From Branch With Tag
>>
>>
>>
>> On Wed, Apr 14, 2021 at 10:22 AM Eric Fetzer 
>> wrote:
>>
>>> Well if I don't tell it what branch to get, how will it get the right
>>> branch?  Sorry, Github is a paradigm shift for me.  I've been using
>>> StarTeam for 20 years and github for just a few weeks now...
>>>
>>>
>> No problem.  Been through that paradigm shift.  Took a long time before
>> the key git concepts finally registered.
>>
>> A git tag represents a specific commit.  A checkout of a tag does not
>> need a branch.  In your case, you're asking for a branch and a tag.  The
>> git plugin decided to give you the branch instead of the tag.  If you only
>> ask for a tag, it will checkout the commit at that tag.
>>
>> Mark Waite
>>
>>
>>> On Wed, Apr 14, 2021 at 10:13 AM Mark Waite 
>>> wrote:
>>>
 Don't use a branch parameter.  Place the tag name in the "Branches to
 build" field.  Compare my screen shots and your screen shots.  You have
 more things in your job definition than I have in mine.  Those extra things
 are causing the behavior you're seeing

 On Wed, Apr 14, 2021 at 8:32 AM Eric Fetzer 
 wrote:

> So I've tried to incorporate what you've said, Mark, but it still just
> clones the tip revision (9.9.9.10 in this case).  Here are my tags:
>
> git show-ref --tags -d
> 4efbdb878c77557d050abbd228fc377adb9419b0 refs/tags/1.0.0.1
> 799eda70c5f052a6f8e757b044b3b60f704a705a refs/tags/1.0.0.1^{}
> c516e3681d2675d4e407b3c26ddfc7da0404c898 refs/tags/1.0.0.2
> 40bf9dd858780d79facfb789921f53d673c08dc9 refs/tags/1.0.0.2^{}
> 9083515085949bfad75f028194226f5a9b1e5ecf refs/tags/9.9.9.10
> 49b0f2cfbf93f36acf6b2124d589a64940eecf18 refs/tags/9.9.9.10^{}
> 019b3f3c634b9071c43f570a62c1191be05c0f4e refs/tags/9.9.9.9
> b2f49473794ad74af0e5943f9292e57e05938fbe refs/tags/9.9.9.9^{}
>
> I'm trying to get 9.9.9.9.  Here is my setup:
>
> [image: image.png]
>
> [image: image.png]
>
> It is honoring the branch specifier for branch, but not for tag.  I've
> tried it with just ${tag_name} as well as with tags/${tag_name} as well as
> refs/tags/${tag_name}.  What am i doing wrong?  Thanks!!!
>
> On Wed, Apr 14, 2021 at 8:06 AM Eric Fetzer 
> wrote:
>
>> Thanks for the detailed description Mark!  Only one thing confuses
>> me, I don't see you specifying the branch to build anywhere in there.  
>> Can
>> you explain that to me because I have to specify the branch as well as 
>> the
>> tag?
>>
>> On Tue, Apr 13, 2021 at 7:42 PM Mark Waite 
>> wrote:
>>
>>>
>>>
>>> On Tue, Apr 13, 2021 at 5:57 PM eric.fetzer 
>>> wrote:
>>>
 I am SO sorry Mark, I confused this Jenkins thread with a totally
 unrelated support ticket.  I'm not using pipeline, just the git plug 
 in in
 conjuction with git parameters.  What exactly do you mean by fetching 
 the
 tags?


>>> I defined a Jenkins Freestyle job that fetches a specific tag and
>>> verifies within the job that the specific tag was fetched.  You can read
>>> the job definition
>>> 
>>> if that helps.
>>>
>>> Crucial portions of the job definition included:
>>>
>>> *Define the parameter for the tag to checkout*
>>>
>>> [image: parameterized-job-definition.png]
>>>
>>> *Use the parameter in the checkout as the local branch name*
>>>
>>> [image: repository-definition.png]
>>>
>>> I believe the default behavior is to fetch tags, but I included it
>>> in the job definition as part of "Advanced clone behaviors" to be 
>>> certain.
>>>
>>> I enabled "Honor refspec on initial clone" because that test
>>> repository is very large and I only wanted a specific branch in the 
>>> clone.
>>>

Re: Git Plugin Checkout From Branch With Tag

[Eric Fetzer]

So here's what blows my mind about a tag.  If I go to the tag in GitHub
Enterprise, it has a .zip and .tar.gz associated with it.  If I unpack that
file, it has the entire contents of the repository in it.  That seems like
a view label to me.  But yet all of the documentation talks about the tag
as a change set.  I don't get it!

On Wed, Apr 14, 2021 at 12:48 PM Mark Waite 
wrote:

>
>
> On Wed, Apr 14, 2021 at 12:16 PM eric.fetzer 
> wrote:
>
>> Thamks Mark!  So how would I go about checking out a branch based on a
>> point in time (a label in most systems)?  Is there a way to snap a label
>> and then check out based on that label or are we resigned to only deal in
>> tip revisions?
>>
>>
> You can checkout a point in time by checking out a specific SHA-1 hash
> that is the most recent commit before that point in time.  See
> https://stackoverflow.com/questions/6990484/how-to-checkout-in-git-by-date
> .
>
>
>>
>>
>> Sent from my T-Mobile 4G LTE Device
>>
>>
>>  Original message 
>> From: Mark Waite 
>> Date: 4/14/21 1:44 PM (GMT-05:00)
>> To: Jenkins Users 
>> Subject: Re: Git Plugin Checkout From Branch With Tag
>>
>>
>>
>> On Wed, Apr 14, 2021 at 10:22 AM Eric Fetzer 
>> wrote:
>>
>>> Well if I don't tell it what branch to get, how will it get the right
>>> branch?  Sorry, Github is a paradigm shift for me.  I've been using
>>> StarTeam for 20 years and github for just a few weeks now...
>>>
>>>
>> No problem.  Been through that paradigm shift.  Took a long time before
>> the key git concepts finally registered.
>>
>> A git tag represents a specific commit.  A checkout of a tag does not
>> need a branch.  In your case, you're asking for a branch and a tag.  The
>> git plugin decided to give you the branch instead of the tag.  If you only
>> ask for a tag, it will checkout the commit at that tag.
>>
>> Mark Waite
>>
>>
>>> On Wed, Apr 14, 2021 at 10:13 AM Mark Waite 
>>> wrote:
>>>
 Don't use a branch parameter.  Place the tag name in the "Branches to
 build" field.  Compare my screen shots and your screen shots.  You have
 more things in your job definition than I have in mine.  Those extra things
 are causing the behavior you're seeing

 On Wed, Apr 14, 2021 at 8:32 AM Eric Fetzer 
 wrote:

> So I've tried to incorporate what you've said, Mark, but it still just
> clones the tip revision (9.9.9.10 in this case).  Here are my tags:
>
> git show-ref --tags -d
> 4efbdb878c77557d050abbd228fc377adb9419b0 refs/tags/1.0.0.1
> 799eda70c5f052a6f8e757b044b3b60f704a705a refs/tags/1.0.0.1^{}
> c516e3681d2675d4e407b3c26ddfc7da0404c898 refs/tags/1.0.0.2
> 40bf9dd858780d79facfb789921f53d673c08dc9 refs/tags/1.0.0.2^{}
> 9083515085949bfad75f028194226f5a9b1e5ecf refs/tags/9.9.9.10
> 49b0f2cfbf93f36acf6b2124d589a64940eecf18 refs/tags/9.9.9.10^{}
> 019b3f3c634b9071c43f570a62c1191be05c0f4e refs/tags/9.9.9.9
> b2f49473794ad74af0e5943f9292e57e05938fbe refs/tags/9.9.9.9^{}
>
> I'm trying to get 9.9.9.9.  Here is my setup:
>
> [image: image.png]
>
> [image: image.png]
>
> It is honoring the branch specifier for branch, but not for tag.  I've
> tried it with just ${tag_name} as well as with tags/${tag_name} as well as
> refs/tags/${tag_name}.  What am i doing wrong?  Thanks!!!
>
> On Wed, Apr 14, 2021 at 8:06 AM Eric Fetzer 
> wrote:
>
>> Thanks for the detailed description Mark!  Only one thing confuses
>> me, I don't see you specifying the branch to build anywhere in there.  
>> Can
>> you explain that to me because I have to specify the branch as well as 
>> the
>> tag?
>>
>> On Tue, Apr 13, 2021 at 7:42 PM Mark Waite 
>> wrote:
>>
>>>
>>>
>>> On Tue, Apr 13, 2021 at 5:57 PM eric.fetzer 
>>> wrote:
>>>
 I am SO sorry Mark, I confused this Jenkins thread with a totally
 unrelated support ticket.  I'm not using pipeline, just the git plug 
 in in
 conjuction with git parameters.  What exactly do you mean by fetching 
 the
 tags?


>>> I defined a Jenkins Freestyle job that fetches a specific tag and
>>> verifies within the job that the specific tag was fetched.  You can read
>>> the job definition
>>> 
>>> if that helps.
>>>
>>> Crucial portions of the job definition included:
>>>
>>> *Define the parameter for the tag to checkout*
>>>
>>> [image: parameterized-job-definition.png]
>>>
>>> *Use the parameter in the checkout as the local branch name*
>>>
>>> [image: repository-definition.png]
>>>
>>> I believe the default behavior is to fetch tags, but I included it
>>> in the job definition as part of "Advanced clone

Re: Git Plugin Checkout From Branch With Tag

[Mark Waite]

On Thu, Apr 15, 2021 at 7:38 AM Eric Fetzer  wrote:

> So when you turn a tag into a release, does it then act more like a label,
> or is it still just a set of changed files?
>
>
Refer to https://git-scm.com/book/en/v2/Git-Basics-Tagging for more details
on the meaning and use of git tags.



> On Wed, Apr 14, 2021 at 12:48 PM Mark Waite 
> wrote:
>
>>
>>
>> On Wed, Apr 14, 2021 at 12:16 PM eric.fetzer 
>> wrote:
>>
>>> Thamks Mark!  So how would I go about checking out a branch based on a
>>> point in time (a label in most systems)?  Is there a way to snap a label
>>> and then check out based on that label or are we resigned to only deal in
>>> tip revisions?
>>>
>>>
>> You can checkout a point in time by checking out a specific SHA-1 hash
>> that is the most recent commit before that point in time.  See
>> https://stackoverflow.com/questions/6990484/how-to-checkout-in-git-by-date
>> .
>>
>>
>>>
>>>
>>> Sent from my T-Mobile 4G LTE Device
>>>
>>>
>>>  Original message 
>>> From: Mark Waite 
>>> Date: 4/14/21 1:44 PM (GMT-05:00)
>>> To: Jenkins Users 
>>> Subject: Re: Git Plugin Checkout From Branch With Tag
>>>
>>>
>>>
>>> On Wed, Apr 14, 2021 at 10:22 AM Eric Fetzer 
>>> wrote:
>>>
 Well if I don't tell it what branch to get, how will it get the right
 branch?  Sorry, Github is a paradigm shift for me.  I've been using
 StarTeam for 20 years and github for just a few weeks now...


>>> No problem.  Been through that paradigm shift.  Took a long time before
>>> the key git concepts finally registered.
>>>
>>> A git tag represents a specific commit.  A checkout of a tag does not
>>> need a branch.  In your case, you're asking for a branch and a tag.  The
>>> git plugin decided to give you the branch instead of the tag.  If you only
>>> ask for a tag, it will checkout the commit at that tag.
>>>
>>> Mark Waite
>>>
>>>
 On Wed, Apr 14, 2021 at 10:13 AM Mark Waite 
 wrote:

> Don't use a branch parameter.  Place the tag name in the "Branches to
> build" field.  Compare my screen shots and your screen shots.  You have
> more things in your job definition than I have in mine.  Those extra 
> things
> are causing the behavior you're seeing
>
> On Wed, Apr 14, 2021 at 8:32 AM Eric Fetzer 
> wrote:
>
>> So I've tried to incorporate what you've said, Mark, but it still
>> just clones the tip revision (9.9.9.10 in this case).  Here are my tags:
>>
>> git show-ref --tags -d
>> 4efbdb878c77557d050abbd228fc377adb9419b0 refs/tags/1.0.0.1
>> 799eda70c5f052a6f8e757b044b3b60f704a705a refs/tags/1.0.0.1^{}
>> c516e3681d2675d4e407b3c26ddfc7da0404c898 refs/tags/1.0.0.2
>> 40bf9dd858780d79facfb789921f53d673c08dc9 refs/tags/1.0.0.2^{}
>> 9083515085949bfad75f028194226f5a9b1e5ecf refs/tags/9.9.9.10
>> 49b0f2cfbf93f36acf6b2124d589a64940eecf18 refs/tags/9.9.9.10^{}
>> 019b3f3c634b9071c43f570a62c1191be05c0f4e refs/tags/9.9.9.9
>> b2f49473794ad74af0e5943f9292e57e05938fbe refs/tags/9.9.9.9^{}
>>
>> I'm trying to get 9.9.9.9.  Here is my setup:
>>
>> [image: image.png]
>>
>> [image: image.png]
>>
>> It is honoring the branch specifier for branch, but not for tag.
>> I've tried it with just ${tag_name} as well as with tags/${tag_name} as
>> well as refs/tags/${tag_name}.  What am i doing wrong?  Thanks!!!
>>
>> On Wed, Apr 14, 2021 at 8:06 AM Eric Fetzer 
>> wrote:
>>
>>> Thanks for the detailed description Mark!  Only one thing confuses
>>> me, I don't see you specifying the branch to build anywhere in there.  
>>> Can
>>> you explain that to me because I have to specify the branch as well as 
>>> the
>>> tag?
>>>
>>> On Tue, Apr 13, 2021 at 7:42 PM Mark Waite <
>>> mark.earl.wa...@gmail.com> wrote:
>>>


 On Tue, Apr 13, 2021 at 5:57 PM eric.fetzer 
 wrote:

> I am SO sorry Mark, I confused this Jenkins thread with a totally
> unrelated support ticket.  I'm not using pipeline, just the git plug 
> in in
> conjuction with git parameters.  What exactly do you mean by fetching 
> the
> tags?
>
>
 I defined a Jenkins Freestyle job that fetches a specific tag and
 verifies within the job that the specific tag was fetched.  You can 
 read
 the job definition
 
 if that helps.

 Crucial portions of the job definition included:

 *Define the parameter for the tag to checkout*

 [image: parameterized-job-definition.png]

 *Use the parameter in the checkout as the local branch name*

 [image: repository-definition.png]
>>>

Re: Git Plugin Checkout From Branch With Tag

[Eric Fetzer]

Thanks Mark!  I'll quit whining and displaying my total git inadequacy,
lol...

On Thu, Apr 15, 2021 at 9:14 AM Mark Waite 
wrote:

>
>
> On Thu, Apr 15, 2021 at 7:38 AM Eric Fetzer  wrote:
>
>> So when you turn a tag into a release, does it then act more like a
>> label, or is it still just a set of changed files?
>>
>>
> Refer to https://git-scm.com/book/en/v2/Git-Basics-Tagging for more
> details on the meaning and use of git tags.
>
>
>
>> On Wed, Apr 14, 2021 at 12:48 PM Mark Waite 
>> wrote:
>>
>>>
>>>
>>> On Wed, Apr 14, 2021 at 12:16 PM eric.fetzer 
>>> wrote:
>>>
 Thamks Mark!  So how would I go about checking out a branch based on a
 point in time (a label in most systems)?  Is there a way to snap a label
 and then check out based on that label or are we resigned to only deal in
 tip revisions?


>>> You can checkout a point in time by checking out a specific SHA-1 hash
>>> that is the most recent commit before that point in time.  See
>>> https://stackoverflow.com/questions/6990484/how-to-checkout-in-git-by-date
>>> .
>>>
>>>


 Sent from my T-Mobile 4G LTE Device


  Original message 
 From: Mark Waite 
 Date: 4/14/21 1:44 PM (GMT-05:00)
 To: Jenkins Users 
 Subject: Re: Git Plugin Checkout From Branch With Tag



 On Wed, Apr 14, 2021 at 10:22 AM Eric Fetzer 
 wrote:

> Well if I don't tell it what branch to get, how will it get the right
> branch?  Sorry, Github is a paradigm shift for me.  I've been using
> StarTeam for 20 years and github for just a few weeks now...
>
>
 No problem.  Been through that paradigm shift.  Took a long time before
 the key git concepts finally registered.

 A git tag represents a specific commit.  A checkout of a tag does not
 need a branch.  In your case, you're asking for a branch and a tag.  The
 git plugin decided to give you the branch instead of the tag.  If you only
 ask for a tag, it will checkout the commit at that tag.

 Mark Waite


> On Wed, Apr 14, 2021 at 10:13 AM Mark Waite 
> wrote:
>
>> Don't use a branch parameter.  Place the tag name in the "Branches to
>> build" field.  Compare my screen shots and your screen shots.  You have
>> more things in your job definition than I have in mine.  Those extra 
>> things
>> are causing the behavior you're seeing
>>
>> On Wed, Apr 14, 2021 at 8:32 AM Eric Fetzer 
>> wrote:
>>
>>> So I've tried to incorporate what you've said, Mark, but it still
>>> just clones the tip revision (9.9.9.10 in this case).  Here are my tags:
>>>
>>> git show-ref --tags -d
>>> 4efbdb878c77557d050abbd228fc377adb9419b0 refs/tags/1.0.0.1
>>> 799eda70c5f052a6f8e757b044b3b60f704a705a refs/tags/1.0.0.1^{}
>>> c516e3681d2675d4e407b3c26ddfc7da0404c898 refs/tags/1.0.0.2
>>> 40bf9dd858780d79facfb789921f53d673c08dc9 refs/tags/1.0.0.2^{}
>>> 9083515085949bfad75f028194226f5a9b1e5ecf refs/tags/9.9.9.10
>>> 49b0f2cfbf93f36acf6b2124d589a64940eecf18 refs/tags/9.9.9.10^{}
>>> 019b3f3c634b9071c43f570a62c1191be05c0f4e refs/tags/9.9.9.9
>>> b2f49473794ad74af0e5943f9292e57e05938fbe refs/tags/9.9.9.9^{}
>>>
>>> I'm trying to get 9.9.9.9.  Here is my setup:
>>>
>>> [image: image.png]
>>>
>>> [image: image.png]
>>>
>>> It is honoring the branch specifier for branch, but not for tag.
>>> I've tried it with just ${tag_name} as well as with tags/${tag_name} as
>>> well as refs/tags/${tag_name}.  What am i doing wrong?  Thanks!!!
>>>
>>> On Wed, Apr 14, 2021 at 8:06 AM Eric Fetzer 
>>> wrote:
>>>
 Thanks for the detailed description Mark!  Only one thing confuses
 me, I don't see you specifying the branch to build anywhere in there.  
 Can
 you explain that to me because I have to specify the branch as well as 
 the
 tag?

 On Tue, Apr 13, 2021 at 7:42 PM Mark Waite <
 mark.earl.wa...@gmail.com> wrote:

>
>
> On Tue, Apr 13, 2021 at 5:57 PM eric.fetzer 
> wrote:
>
>> I am SO sorry Mark, I confused this Jenkins thread with a totally
>> unrelated support ticket.  I'm not using pipeline, just the git plug 
>> in in
>> conjuction with git parameters.  What exactly do you mean by 
>> fetching the
>> tags?
>>
>>
> I defined a Jenkins Freestyle job that fetches a specific tag and
> verifies within the job that the specific tag was fetched.  You can 
> read
> the job definition
> 
> if that helps.
>
> Crucial portions of the job definition

Re: Git Plugin Checkout From Branch With Tag

[Mark Waite]

Not taken as whining, just that any attempt I made to explain would be
riddled with inadequacies and misuse of terminology.  The definitive
documentation has more reviewers and more people that try to assure it is
correct, complete, and consistent.

On Thu, Apr 15, 2021 at 9:19 AM Eric Fetzer  wrote:

> Thanks Mark!  I'll quit whining and displaying my total git inadequacy,
> lol...
>
> On Thu, Apr 15, 2021 at 9:14 AM Mark Waite 
> wrote:
>
>>
>>
>> On Thu, Apr 15, 2021 at 7:38 AM Eric Fetzer 
>> wrote:
>>
>>> So when you turn a tag into a release, does it then act more like a
>>> label, or is it still just a set of changed files?
>>>
>>>
>> Refer to https://git-scm.com/book/en/v2/Git-Basics-Tagging for more
>> details on the meaning and use of git tags.
>>
>>
>>
>>> On Wed, Apr 14, 2021 at 12:48 PM Mark Waite 
>>> wrote:
>>>


 On Wed, Apr 14, 2021 at 12:16 PM eric.fetzer 
 wrote:

> Thamks Mark!  So how would I go about checking out a branch based on a
> point in time (a label in most systems)?  Is there a way to snap a label
> and then check out based on that label or are we resigned to only deal in
> tip revisions?
>
>
 You can checkout a point in time by checking out a specific SHA-1 hash
 that is the most recent commit before that point in time.  See
 https://stackoverflow.com/questions/6990484/how-to-checkout-in-git-by-date
 .


>
>
> Sent from my T-Mobile 4G LTE Device
>
>
>  Original message 
> From: Mark Waite 
> Date: 4/14/21 1:44 PM (GMT-05:00)
> To: Jenkins Users 
> Subject: Re: Git Plugin Checkout From Branch With Tag
>
>
>
> On Wed, Apr 14, 2021 at 10:22 AM Eric Fetzer 
> wrote:
>
>> Well if I don't tell it what branch to get, how will it get the right
>> branch?  Sorry, Github is a paradigm shift for me.  I've been using
>> StarTeam for 20 years and github for just a few weeks now...
>>
>>
> No problem.  Been through that paradigm shift.  Took a long time
> before the key git concepts finally registered.
>
> A git tag represents a specific commit.  A checkout of a tag does not
> need a branch.  In your case, you're asking for a branch and a tag.  The
> git plugin decided to give you the branch instead of the tag.  If you only
> ask for a tag, it will checkout the commit at that tag.
>
> Mark Waite
>
>
>> On Wed, Apr 14, 2021 at 10:13 AM Mark Waite <
>> mark.earl.wa...@gmail.com> wrote:
>>
>>> Don't use a branch parameter.  Place the tag name in the "Branches
>>> to build" field.  Compare my screen shots and your screen shots.  You 
>>> have
>>> more things in your job definition than I have in mine.  Those extra 
>>> things
>>> are causing the behavior you're seeing
>>>
>>> On Wed, Apr 14, 2021 at 8:32 AM Eric Fetzer 
>>> wrote:
>>>
 So I've tried to incorporate what you've said, Mark, but it still
 just clones the tip revision (9.9.9.10 in this case).  Here are my 
 tags:

 git show-ref --tags -d
 4efbdb878c77557d050abbd228fc377adb9419b0 refs/tags/1.0.0.1
 799eda70c5f052a6f8e757b044b3b60f704a705a refs/tags/1.0.0.1^{}
 c516e3681d2675d4e407b3c26ddfc7da0404c898 refs/tags/1.0.0.2
 40bf9dd858780d79facfb789921f53d673c08dc9 refs/tags/1.0.0.2^{}
 9083515085949bfad75f028194226f5a9b1e5ecf refs/tags/9.9.9.10
 49b0f2cfbf93f36acf6b2124d589a64940eecf18 refs/tags/9.9.9.10^{}
 019b3f3c634b9071c43f570a62c1191be05c0f4e refs/tags/9.9.9.9
 b2f49473794ad74af0e5943f9292e57e05938fbe refs/tags/9.9.9.9^{}

 I'm trying to get 9.9.9.9.  Here is my setup:

 [image: image.png]

 [image: image.png]

 It is honoring the branch specifier for branch, but not for tag.
 I've tried it with just ${tag_name} as well as with tags/${tag_name} as
 well as refs/tags/${tag_name}.  What am i doing wrong?  Thanks!!!

 On Wed, Apr 14, 2021 at 8:06 AM Eric Fetzer 
 wrote:

> Thanks for the detailed description Mark!  Only one thing confuses
> me, I don't see you specifying the branch to build anywhere in there. 
>  Can
> you explain that to me because I have to specify the branch as well 
> as the
> tag?
>
> On Tue, Apr 13, 2021 at 7:42 PM Mark Waite <
> mark.earl.wa...@gmail.com> wrote:
>
>>
>>
>> On Tue, Apr 13, 2021 at 5:57 PM eric.fetzer <
>> eric.fet...@gmail.com> wrote:
>>
>>> I am SO sorry Mark, I confused this Jenkins thread with a
>>> totally unrelated support ticket.  I'm not using pipeline, just the 
>>> git
>>> plug in in conjuction with git parameters.  What exactly do you 
>>> mean by
>

How to fix workspace deletion on slave node

[DHAVAL JAISWAL]

Workspace on Slave node is deleted if the Job is not running/active from
Master Jenkins for some days.

How shall I fix this issue?

While referring to some forum advising to fix
*hudson.model.WorkspaceCleanupThread.disabled* [ false ]. However, I am
unable to find this parameter.

Guide me on how can I fix this issuer permanently & save my workspace and
build.

I see one option in Jenkins is DISCARD OLD BUILD. However, I assume that
check is to retain the build (to see the history) on Master Jenkins.

If needed I can help with some more information.

-- 
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/CAH5ShBiSTXMYHuhW%2Bthxj3yMAvAOQWqcxgAUJwSM7ZM4kvGBYA%40mail.gmail.com.

Re: Git Plugin Checkout From Branch With Tag

[Eric Fetzer]

Thanks Mark!

On Thu, Apr 15, 2021 at 9:22 AM Mark Waite 
wrote:

> Not taken as whining, just that any attempt I made to explain would be
> riddled with inadequacies and misuse of terminology.  The definitive
> documentation has more reviewers and more people that try to assure it is
> correct, complete, and consistent.
>
> On Thu, Apr 15, 2021 at 9:19 AM Eric Fetzer  wrote:
>
>> Thanks Mark!  I'll quit whining and displaying my total git inadequacy,
>> lol...
>>
>> On Thu, Apr 15, 2021 at 9:14 AM Mark Waite 
>> wrote:
>>
>>>
>>>
>>> On Thu, Apr 15, 2021 at 7:38 AM Eric Fetzer 
>>> wrote:
>>>
 So when you turn a tag into a release, does it then act more like a
 label, or is it still just a set of changed files?


>>> Refer to https://git-scm.com/book/en/v2/Git-Basics-Tagging for more
>>> details on the meaning and use of git tags.
>>>
>>>
>>>
 On Wed, Apr 14, 2021 at 12:48 PM Mark Waite 
 wrote:

>
>
> On Wed, Apr 14, 2021 at 12:16 PM eric.fetzer 
> wrote:
>
>> Thamks Mark!  So how would I go about checking out a branch based on
>> a point in time (a label in most systems)?  Is there a way to snap a 
>> label
>> and then check out based on that label or are we resigned to only deal in
>> tip revisions?
>>
>>
> You can checkout a point in time by checking out a specific SHA-1 hash
> that is the most recent commit before that point in time.  See
> https://stackoverflow.com/questions/6990484/how-to-checkout-in-git-by-date
> .
>
>
>>
>>
>> Sent from my T-Mobile 4G LTE Device
>>
>>
>>  Original message 
>> From: Mark Waite 
>> Date: 4/14/21 1:44 PM (GMT-05:00)
>> To: Jenkins Users 
>> Subject: Re: Git Plugin Checkout From Branch With Tag
>>
>>
>>
>> On Wed, Apr 14, 2021 at 10:22 AM Eric Fetzer 
>> wrote:
>>
>>> Well if I don't tell it what branch to get, how will it get the
>>> right branch?  Sorry, Github is a paradigm shift for me.  I've been 
>>> using
>>> StarTeam for 20 years and github for just a few weeks now...
>>>
>>>
>> No problem.  Been through that paradigm shift.  Took a long time
>> before the key git concepts finally registered.
>>
>> A git tag represents a specific commit.  A checkout of a tag does not
>> need a branch.  In your case, you're asking for a branch and a tag.  The
>> git plugin decided to give you the branch instead of the tag.  If you 
>> only
>> ask for a tag, it will checkout the commit at that tag.
>>
>> Mark Waite
>>
>>
>>> On Wed, Apr 14, 2021 at 10:13 AM Mark Waite <
>>> mark.earl.wa...@gmail.com> wrote:
>>>
 Don't use a branch parameter.  Place the tag name in the "Branches
 to build" field.  Compare my screen shots and your screen shots.  You 
 have
 more things in your job definition than I have in mine.  Those extra 
 things
 are causing the behavior you're seeing

 On Wed, Apr 14, 2021 at 8:32 AM Eric Fetzer 
 wrote:

> So I've tried to incorporate what you've said, Mark, but it still
> just clones the tip revision (9.9.9.10 in this case).  Here are my 
> tags:
>
> git show-ref --tags -d
> 4efbdb878c77557d050abbd228fc377adb9419b0 refs/tags/1.0.0.1
> 799eda70c5f052a6f8e757b044b3b60f704a705a refs/tags/1.0.0.1^{}
> c516e3681d2675d4e407b3c26ddfc7da0404c898 refs/tags/1.0.0.2
> 40bf9dd858780d79facfb789921f53d673c08dc9 refs/tags/1.0.0.2^{}
> 9083515085949bfad75f028194226f5a9b1e5ecf refs/tags/9.9.9.10
> 49b0f2cfbf93f36acf6b2124d589a64940eecf18 refs/tags/9.9.9.10^{}
> 019b3f3c634b9071c43f570a62c1191be05c0f4e refs/tags/9.9.9.9
> b2f49473794ad74af0e5943f9292e57e05938fbe refs/tags/9.9.9.9^{}
>
> I'm trying to get 9.9.9.9.  Here is my setup:
>
> [image: image.png]
>
> [image: image.png]
>
> It is honoring the branch specifier for branch, but not for tag.
> I've tried it with just ${tag_name} as well as with tags/${tag_name} 
> as
> well as refs/tags/${tag_name}.  What am i doing wrong?  Thanks!!!
>
> On Wed, Apr 14, 2021 at 8:06 AM Eric Fetzer 
> wrote:
>
>> Thanks for the detailed description Mark!  Only one thing
>> confuses me, I don't see you specifying the branch to build anywhere 
>> in
>> there.  Can you explain that to me because I have to specify the 
>> branch as
>> well as the tag?
>>
>> On Tue, Apr 13, 2021 at 7:42 PM Mark Waite <
>> mark.earl.wa...@gmail.com> wrote:
>>
>>>
>>>
>>> On Tue, Apr 13, 2021 at 5:57 PM eric.fetzer <
>>> eric.fet...@gmail.com> wrote:
>>>
 I am SO sorry Mark,

Re: How to fix workspace deletion on slave node

[Senthil Nathan]

This is a system property that should be set when starting up jenkins. You
would want to set *hudson.model.WorkspaceCleanupThread.disabled*  to true
to disable deletion of workspaces.

Usage is documented here:
https://www.jenkins.io/doc/book/managing/system-properties/

On Thu, Apr 15, 2021 at 11:09 AM DHAVAL JAISWAL  wrote:

> Workspace on Slave node is deleted if the Job is not running/active from
> Master Jenkins for some days.
>
> How shall I fix this issue?
>
> While referring to some forum advising to fix
> *hudson.model.WorkspaceCleanupThread.disabled* [ false ]. However, I am
> unable to find this parameter.
>
> Guide me on how can I fix this issuer permanently & save my workspace and
> build.
>
> I see one option in Jenkins is DISCARD OLD BUILD. However, I assume that
> check is to retain the build (to see the history) on Master Jenkins.
>
> If needed I can help with some more information.
>
> --
> 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/CAH5ShBiSTXMYHuhW%2Bthxj3yMAvAOQWqcxgAUJwSM7ZM4kvGBYA%40mail.gmail.com
> 
> .
>

-- 
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/CAJgiyW9Z95e8KO%3D-gKr9pXXB82rG6JmZwMEUmbgjQw-zyq_gSA%40mail.gmail.com.

Re: Git Plugin Checkout From Branch With Tag

['Dirk Heinrichs' via Jenkins Users]

Am Donnerstag, den 15.04.2021, 08:47 -0600 schrieb Eric Fetzer:

> So here's what blows my mind about a tag.  If I go to the tag in
> GitHub Enterprise, it has a .zip and .tar.gz associated with it.  If
> I unpack that file, it has the entire contents of the repository in
> it.  That seems like a view label to me.  But yet all of the
> documentation talks about the tag as a change set.  I don't get it!

GitHub, GitLab, , and all those sites are NOT Git.
They are collaboration platforms that use Git for source code
management and offer some additional tooling around it. One such offer
is to allow the user to download a ZIP or Tar archive of a particular
state of a repository (i.o.w.: a snapshot, w/o the history), which can
be identified by a Git tag, but also by a changeset identifier (for
example: 
https://github.com/saltstack/salt/archive/d240e450f449f16ef176a9cb563b9f0447687a6e.zip
). These are usually created on the fly when someone requests the
download.

Speaking of Git tags (or branches): They're all the same, a reference
to a specific changeset. The only difference is that branch refs are a
moving target (they always reference the latest changeset of a
particular branch of development), while tags are not.

HTH...

Dirk
-- 
Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
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/eed9236d95231f0893d0e6a90bc399e28ade9564.camel%40opentext.com.


signature.asc
Description: This is a digitally signed message part