Re: GitHub webhooks, where to put smee client if Jenkins is in a container?

[Michael Neale]

Hi Craig, glad that post is getting mileage!

So in kubernetes, I guess that would be adding to the pod that is running
your Jenkins container: there would be a pod definition (not sure if you
wrote it) somewhere, and you could cook up an image with smee running and
have it as a "sidecar" next to the Jenkins container, as pods share a
network and anything running in the pod could access the /github-webhook/
endpoint

https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/ (look for
sidecar)

So then it depends how you deployed that image into a pod (but to start
with would need to cook up an image with smee in it ready to go - I am not
sure if one exists yet).



On Thu, Oct 24, 2019 at 5:39 PM Craig Rodrigues 
wrote:

> Michael,
>
> In your blog post:
>
> "Triggering builds with webhooks behind a secure firewall"
> https://jenkins.io/blog/2019/01/07/webhook-firewalls/
>
> You gave a good overview of how someone can use webhooks
> invoked from GitHub in the cloud, to a Jenkins server which exists behind
> a firewall, using https://smee.io .
>
> In your post, you mention:
>
> *"you should install the smee client next to where you have the Jenkins
> server running:*"
>
> In my case, I am running the jenkins/jenkins:lts docker image
> ( https://hub.docker.com/r/jenkins/jenkins/ ), which is deployed by
> Kubernetes 1.14.
> My Jenkins setup is behind a firewall.
> However, my source code exists on GitHub which exists in the public cloud.
>
> Since I do not want to modify the jenkins/jenkins:lts docker image,
> where can I run the smee client, so that I can still use it
> with my setup?
>
> I'd like to get webhooks from the public GitHub triggering builds on
> my Jenkins server running behind a firewall.
>
> Thanks.
>
> --
> Craig
>

-- 
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/CAEuC6Lj49iophCDoF%3DzsfMJu%3DrghQfjBTSdqXrHxksE6aEj0Vw%40mail.gmail.com.

Re: Getting user who created a pull request with Jenkins pipeline

[Eberhard Beilharz]

Answering (part of) my own question: there's an environment variable 
CHANGE_AUTHOR that gets set on a PR. There's also the 
pipeline-github-plugin that provides information about a PR.

Now to figure out how to find out if the change author is a 
member/collaborator or not...

-- 
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/601db8fb-8f13-4dfa-bbaf-4595629053f7%40googlegroups.com.

Trying to get Github events like "commit comments and pushes" to build the jenkins pipeline Job

[kishore babu]

Based on the commit comment, I would like to trigger the Pipeline Job.
Firstly unable to get the commit trigger to build the Pipeline Job.
Can someone suggest the best practice?

Currently, im using Github enterprise server and Local hosted Jenkins 
server.
I'm able to get the pull request using Github pull request builder 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/f5ea9fc1-f7a1-4238-9abb-fe70dd4c9061%40googlegroups.com.

Re: GitHub webhook push CI issue with pipeline projects

[kishore babu]

I hope you got the solution, If you could suggest me the best practice it 
will be helpful for me.

On Friday, 11 November 2016 09:18:12 UTC+5:30, Cory Grubbs wrote:
>
> Okstill doesn't solve the problem of having to have two separate 
> Jenkins projects for every build which is not efficient nor scalable to the 
> level I need it to be. 
>
> I find it hard to believe you can't configure a webhook on a github repo 
> to kick off a specific Jenkins job that isn't connected to the repo but I 
> sure can't figure out how. 
>
> What is the purpose of the Github project field within the Jenkins job 
> configuration if it doesn't create the necessary association for webhooks 
> to invoke the job when changes are pushed to the specified github repo?
>
> Cory
>
>

-- 
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/b2dba239-69e5-4187-872f-3b8b94e20aae%40googlegroups.com.

GitHub webhooks, where to put smee client if Jenkins is in a container?

[Craig Rodrigues]

Michael,

In your blog post:

"Triggering builds with webhooks behind a secure firewall"
https://jenkins.io/blog/2019/01/07/webhook-firewalls/

You gave a good overview of how someone can use webhooks
invoked from GitHub in the cloud, to a Jenkins server which exists behind
a firewall, using https://smee.io .

In your post, you mention:

*"you should install the smee client next to where you have the Jenkins
server running:*"

In my case, I am running the jenkins/jenkins:lts docker image
( https://hub.docker.com/r/jenkins/jenkins/ ), which is deployed by
Kubernetes 1.14.
My Jenkins setup is behind a firewall.
However, my source code exists on GitHub which exists in the public cloud.

Since I do not want to modify the jenkins/jenkins:lts docker image,
where can I run the smee client, so that I can still use it
with my setup?

I'd like to get webhooks from the public GitHub triggering builds on
my Jenkins server running behind a firewall.

Thanks.

--
Craig

-- 
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/CAG%3DrPVdT6EKnXP-c%2BzNa6ZDOYkmR%2BbbbWHvKt2K3dXAWujzcUQ%40mail.gmail.com.

How to enable "recordIssues tool: pyLint"

[tOmMy Lau]

Hi,
I'm a new fish on Jenkins, I saw one of this pipeline code
recordIssues tool: pyLint(pattern: '.test_reports/pylint.out'), 
enabledForFailure: true

I found it's interesting and added into my Jenkinsfile, however, when my 
job runs at this line, it throws error as below:

java.lang.NoSuchMethodError: No such DSL method 'pyLint' found among steps

..



So, my question is: is there any plugins need to be installed? I searched 
plugins but not find pyLint plugin.


Thanks.

tOmMy

-- 
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/c3a1504d-f597-4037-a3e9-bd9539acabc2%40googlegroups.com.

Re: How to enable "recordIssues tool: pyLint"

[Ullrich Hafner]

You need to install the warnings-ng plugin: 
https://github.com/jenkinsci/warnings-ng-plugin 


For more details please ask in our Gitter channel: 
https://gitter.im/jenkinsci/warnings-plugin 


> Am 24.10.2019 um 10:31 schrieb tOmMy Lau :
> 
> Hi,
> I'm a new fish on Jenkins, I saw one of this pipeline code
> recordIssues tool: pyLint(pattern: '.test_reports/pylint.out'), 
> enabledForFailure: true
> 
> I found it's interesting and added into my Jenkinsfile, however, when my job 
> runs at this line, it throws error as below:
> java.lang.NoSuchMethodError: No such DSL method 'pyLint' found among steps
> ..
> 
> 
> So, my question is: is there any plugins need to be installed? I searched 
> plugins but not find pyLint plugin.
> 
> Thanks.
> tOmMy
> 
> -- 
> 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/c3a1504d-f597-4037-a3e9-bd9539acabc2%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/6D7DDF7D-79D6-40E6-91E8-64A59579DA6E%40gmail.com.

[Jenkins X] What are the best practices for upgrading/adding Jenkins plugins?

[Andy Hopper]

Hello! First: I'm used to Jenkins, but I'm a JX noob.

We just set up a Jenkins X installation, and I see that a lot of the 
plugins are outdated. It appears that upgrading them directly in Jenkins is 
not a good idea as those changes will not be persisted. What are the best 
practices for upgrading/adding Jenkins plugins in this shiny new world?

-- 
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/b689e490-0596-47a9-9c35-1bae6b0a771c%40googlegroups.com.

Re: GitHub webhooks, where to put smee client if Jenkins is in a container?

[Craig Rodrigues]

This seems unnecessarily complicated.
Why does the smee client need to be next to the Jenkins server at all?

If I was not using Kubernetes, and if I had two separate physical machines,
one running Jenkins and one running smee,
would it be possible for smee to interact with Jenkins via the REST API?

--
Craig

On Thu, Oct 24, 2019 at 1:01 AM Michael Neale  wrote:

> Hi Craig, glad that post is getting mileage!
>
> So in kubernetes, I guess that would be adding to the pod that is running
> your Jenkins container: there would be a pod definition (not sure if you
> wrote it) somewhere, and you could cook up an image with smee running and
> have it as a "sidecar" next to the Jenkins container, as pods share a
> network and anything running in the pod could access the /github-webhook/
> endpoint
>
> https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/ (look
> for sidecar)
>
> So then it depends how you deployed that image into a pod (but to start
> with would need to cook up an image with smee in it ready to go - I am not
> sure if one exists yet).
>
>
>
> On Thu, Oct 24, 2019 at 5:39 PM Craig Rodrigues 
> wrote:
>
>> Michael,
>>
>> In your blog post:
>>
>> "Triggering builds with webhooks behind a secure firewall"
>> https://jenkins.io/blog/2019/01/07/webhook-firewalls/
>>
>> You gave a good overview of how someone can use webhooks
>> invoked from GitHub in the cloud, to a Jenkins server which exists behind
>> a firewall, using https://smee.io .
>>
>> In your post, you mention:
>>
>> *"you should install the smee client next to where you have the Jenkins
>> server running:*"
>>
>> In my case, I am running the jenkins/jenkins:lts docker image
>> ( https://hub.docker.com/r/jenkins/jenkins/ ), which is deployed by
>> Kubernetes 1.14.
>> My Jenkins setup is behind a firewall.
>> However, my source code exists on GitHub which exists in the public cloud.
>>
>> Since I do not want to modify the jenkins/jenkins:lts docker image,
>> where can I run the smee client, so that I can still use it
>> with my setup?
>>
>> I'd like to get webhooks from the public GitHub triggering builds on
>> my Jenkins server running behind a firewall.
>>
>> Thanks.
>>
>> --
>> Craig
>>
>
>
>

-- 
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/CAG%3DrPVctnm3WkK4dWUViwdFbemDK0caLrMacq7JmPa0ZnS3T%3Dw%40mail.gmail.com.

Timestamper 1.9+ - how to deal with added content (timestamps) in build logs.

[Austin Witt]

Several Jenkins masters that I care about have recently upgraded the 
Timestamper plugin to 1.10 from 1.8. This pulls in the relatively large 
change in 1.9 of *timestamps actually being written to the build logs* instead 
of handled as metadata. The "View as Plain Text" link and /consoleText urls 
now serve build logs with timestamps in them!

I also have code that parses Jenkins build logs, looking for specific 
output from various tools. The addition of timestamps has broken this 
detection. Complicating my situation is the fact that my code needs to be 
able to parse Jenkins logs from masters regardless of whether or not they 
are running the Timestamper plugin - so I cannot simply start checking for 
the timestamper's timestamps, as they may not be there.

For me, the best behavior was the original behavior: when Timestamper 
stored the timestamps as metadata and left the build logs pure - as they 
were emitted during the build. I understand that *for now*, I can just 
downgrade the Timestamper plugin and tell people not to upgrade, but that 
won't work forever.

Has anyone else had to contend with the Timestamper's modification of the 
"real" build logs conflicting with code that tries to read the logs? What 
did you do?

Has anyone considered or asked for an option in the Timestamper plugin to 
choose the old behavior instead? When discussing the redesign of 
Timestamper, did this issue come up?

If there's a more-appropriate venue to ask this question, please let me 
know. Thank you!

-- 
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/89cb8616-dd6d-46db-a492-99a05fd7afe0%40googlegroups.com.

Re: GitHub webhooks, where to put smee client if Jenkins is in a container?

[Michael Neale]

yeah fair point it doesn't have to be right next to it - but it has to be
somewhere it can reach /github-webhook endpoint - so could be a totally
separate app? (as long as your Jenkins master instance is discoverable and
accessible from elsewhere from the cluster - which I guess it would be
right?). It only uses the REST api, and only the /github-webhook endpoint,
nothing else.

On Fri, Oct 25, 2019 at 1:18 AM Craig Rodrigues 
wrote:

> This seems unnecessarily complicated.
> Why does the smee client need to be next to the Jenkins server at all?
>
> If I was not using Kubernetes, and if I had two separate physical machines,
> one running Jenkins and one running smee,
> would it be possible for smee to interact with Jenkins via the REST API?
>
> --
> Craig
>
> On Thu, Oct 24, 2019 at 1:01 AM Michael Neale 
> wrote:
>
>> Hi Craig, glad that post is getting mileage!
>>
>> So in kubernetes, I guess that would be adding to the pod that is running
>> your Jenkins container: there would be a pod definition (not sure if you
>> wrote it) somewhere, and you could cook up an image with smee running and
>> have it as a "sidecar" next to the Jenkins container, as pods share a
>> network and anything running in the pod could access the /github-webhook/
>> endpoint
>>
>> https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/ (look
>> for sidecar)
>>
>> So then it depends how you deployed that image into a pod (but to start
>> with would need to cook up an image with smee in it ready to go - I am not
>> sure if one exists yet).
>>
>>
>>
>> On Thu, Oct 24, 2019 at 5:39 PM Craig Rodrigues 
>> wrote:
>>
>>> Michael,
>>>
>>> In your blog post:
>>>
>>> "Triggering builds with webhooks behind a secure firewall"
>>> https://jenkins.io/blog/2019/01/07/webhook-firewalls/
>>>
>>> You gave a good overview of how someone can use webhooks
>>> invoked from GitHub in the cloud, to a Jenkins server which exists behind
>>> a firewall, using https://smee.io .
>>>
>>> In your post, you mention:
>>>
>>> *"you should install the smee client next to where you have the Jenkins
>>> server running:*"
>>>
>>> In my case, I am running the jenkins/jenkins:lts docker image
>>> ( https://hub.docker.com/r/jenkins/jenkins/ ), which is deployed by
>>> Kubernetes 1.14.
>>> My Jenkins setup is behind a firewall.
>>> However, my source code exists on GitHub which exists in the public
>>> cloud.
>>>
>>> Since I do not want to modify the jenkins/jenkins:lts docker image,
>>> where can I run the smee client, so that I can still use it
>>> with my setup?
>>>
>>> I'd like to get webhooks from the public GitHub triggering builds on
>>> my Jenkins server running behind a firewall.
>>>
>>> Thanks.
>>>
>>> --
>>> Craig
>>>
>>
>>
>>

-- 
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/CAEuC6LgqSMZaGETCSZEVvzDsW60HaOJYDhqOnSm0mSvUyOzXaQ%40mail.gmail.com.

Re: GitHub webhooks, where to put smee client if Jenkins is in a container?

[Craig Rodrigues]

Awesome!  So I could run the smee client on a separate physical host, but
with network connectivity to my Jenkins server.
Both the smee client and the Jenkins server would be behind the firewall.

To be cool, I could Dockerize the smee client, and deploy that in my
Kubernetes cluster.  However, I want to understand
how the pieces fit together before I do that.

One other question, which organization is behind https://smee.io/ ?
If I do a whois lookup, I see: Registrant Organization: GitHub, Inc.

Is this a fully supported service of GitHub, or a side project?

I don't want to try using a service which may disappear.
--
Craig

On Thu, Oct 24, 2019 at 2:39 PM Michael Neale  wrote:

> yeah fair point it doesn't have to be right next to it - but it has to be
> somewhere it can reach /github-webhook endpoint - so could be a totally
> separate app? (as long as your Jenkins master instance is discoverable and
> accessible from elsewhere from the cluster - which I guess it would be
> right?). It only uses the REST api, and only the /github-webhook endpoint,
> nothing else.
>
> On Fri, Oct 25, 2019 at 1:18 AM Craig Rodrigues 
> wrote:
>
>> This seems unnecessarily complicated.
>> Why does the smee client need to be next to the Jenkins server at all?
>>
>> If I was not using Kubernetes, and if I had two separate physical
>> machines,
>> one running Jenkins and one running smee,
>> would it be possible for smee to interact with Jenkins via the REST API?
>>
>> --
>> Craig
>>
>> On Thu, Oct 24, 2019 at 1:01 AM Michael Neale 
>> wrote:
>>
>>> Hi Craig, glad that post is getting mileage!
>>>
>>> So in kubernetes, I guess that would be adding to the pod that is
>>> running your Jenkins container: there would be a pod definition (not sure
>>> if you wrote it) somewhere, and you could cook up an image with smee
>>> running and have it as a "sidecar" next to the Jenkins container, as pods
>>> share a network and anything running in the pod could access the
>>> /github-webhook/ endpoint
>>>
>>> https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/ (look
>>> for sidecar)
>>>
>>> So then it depends how you deployed that image into a pod (but to start
>>> with would need to cook up an image with smee in it ready to go - I am not
>>> sure if one exists yet).
>>>
>>>
>>>
>>> On Thu, Oct 24, 2019 at 5:39 PM Craig Rodrigues 
>>> wrote:
>>>
 Michael,

 In your blog post:

 "Triggering builds with webhooks behind a secure firewall"
 https://jenkins.io/blog/2019/01/07/webhook-firewalls/

 You gave a good overview of how someone can use webhooks
 invoked from GitHub in the cloud, to a Jenkins server which exists
 behind
 a firewall, using https://smee.io .

 In your post, you mention:

 *"you should install the smee client next to where you have the Jenkins
 server running:*"

 In my case, I am running the jenkins/jenkins:lts docker image
 ( https://hub.docker.com/r/jenkins/jenkins/ ), which is deployed by
 Kubernetes 1.14.
 My Jenkins setup is behind a firewall.
 However, my source code exists on GitHub which exists in the public
 cloud.

 Since I do not want to modify the jenkins/jenkins:lts docker image,
 where can I run the smee client, so that I can still use it
 with my setup?

 I'd like to get webhooks from the public GitHub triggering builds on
 my Jenkins server running behind a firewall.

 Thanks.

 --
 Craig

>>>
>>>
>>>
>
>

-- 
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/CAG%3DrPVeqUdpJUCzecSyb%2BHmLO4X2hGkCzaNWRnbS8Y9oDP%2B2sA%40mail.gmail.com.

Re: GitHub webhooks, where to put smee client if Jenkins is in a container?

[Michael Neale]

yeah - as long as it can post the webhook, it can run anywhere it needs to.

It is run by github, but not sure of its officially supported status (they
also open source the code to it)

On Fri, Oct 25, 2019 at 11:10 AM Craig Rodrigues 
wrote:

> Awesome!  So I could run the smee client on a separate physical host, but
> with network connectivity to my Jenkins server.
> Both the smee client and the Jenkins server would be behind the firewall.
>
> To be cool, I could Dockerize the smee client, and deploy that in my
> Kubernetes cluster.  However, I want to understand
> how the pieces fit together before I do that.
>
> One other question, which organization is behind https://smee.io/ ?
> If I do a whois lookup, I see: Registrant Organization: GitHub, Inc.
>
> Is this a fully supported service of GitHub, or a side project?
>
> I don't want to try using a service which may disappear.
> --
> Craig
>
> On Thu, Oct 24, 2019 at 2:39 PM Michael Neale 
> wrote:
>
>> yeah fair point it doesn't have to be right next to it - but it has to be
>> somewhere it can reach /github-webhook endpoint - so could be a totally
>> separate app? (as long as your Jenkins master instance is discoverable and
>> accessible from elsewhere from the cluster - which I guess it would be
>> right?). It only uses the REST api, and only the /github-webhook endpoint,
>> nothing else.
>>
>> On Fri, Oct 25, 2019 at 1:18 AM Craig Rodrigues 
>> wrote:
>>
>>> This seems unnecessarily complicated.
>>> Why does the smee client need to be next to the Jenkins server at all?
>>>
>>> If I was not using Kubernetes, and if I had two separate physical
>>> machines,
>>> one running Jenkins and one running smee,
>>> would it be possible for smee to interact with Jenkins via the REST API?
>>>
>>> --
>>> Craig
>>>
>>> On Thu, Oct 24, 2019 at 1:01 AM Michael Neale 
>>> wrote:
>>>
 Hi Craig, glad that post is getting mileage!

 So in kubernetes, I guess that would be adding to the pod that is
 running your Jenkins container: there would be a pod definition (not sure
 if you wrote it) somewhere, and you could cook up an image with smee
 running and have it as a "sidecar" next to the Jenkins container, as pods
 share a network and anything running in the pod could access the
 /github-webhook/ endpoint

 https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/ (look
 for sidecar)

 So then it depends how you deployed that image into a pod (but to start
 with would need to cook up an image with smee in it ready to go - I am not
 sure if one exists yet).



 On Thu, Oct 24, 2019 at 5:39 PM Craig Rodrigues 
 wrote:

> Michael,
>
> In your blog post:
>
> "Triggering builds with webhooks behind a secure firewall"
> https://jenkins.io/blog/2019/01/07/webhook-firewalls/
>
> You gave a good overview of how someone can use webhooks
> invoked from GitHub in the cloud, to a Jenkins server which exists
> behind
> a firewall, using https://smee.io .
>
> In your post, you mention:
>
> *"you should install the smee client next to where you have the
> Jenkins server running:*"
>
> In my case, I am running the jenkins/jenkins:lts docker image
> ( https://hub.docker.com/r/jenkins/jenkins/ ), which is deployed by
> Kubernetes 1.14.
> My Jenkins setup is behind a firewall.
> However, my source code exists on GitHub which exists in the public
> cloud.
>
> Since I do not want to modify the jenkins/jenkins:lts docker image,
> where can I run the smee client, so that I can still use it
> with my setup?
>
> I'd like to get webhooks from the public GitHub triggering builds on
> my Jenkins server running behind a firewall.
>
> Thanks.
>
> --
> Craig
>



>>
>>

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

How to properly use ${FILE,path=foo.txt} in Jenkins?

[Ilia Basin]

Hi.
I'm trying to use the syntax `${FILE,path=foo.txt}` to  introduced in Token 
Macro Plugin 1.11. My plugin version is 1.12.1
In what context can this be used? My project is a freestyle project. It 
creates foo.txt, then I have the EnvInject step with the following:

AAA=${FILE,path=foo.txt}

and then the shell step:

echo "AAA=$AAA"

Here's the console output:

[basintest] $ /u01/jenkins/jenkins_shell -xe 
/tmp/hudson8306494744167210672.sh
+ . /tmp/hudson8306494744167210672.sh
++ cat foo.txt
aaa
[EnvInject] - Injecting environment variables from a build step.
[EnvInject] - Injecting as environment variables the properties content 
AAA=${FILE,path=foo.txt}

[EnvInject] - Variables injected successfully.
[basintest] $ /u01/jenkins/jenkins_shell -xe 
/tmp/hudson6182970742482538021.sh
+ . /tmp/hudson6182970742482538021.sh
++ echo 'AAA=${FILE,path=foo.txt}'
AAA=${FILE,path=foo.txt}
Finished: SUCCESS

-- 
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/c745bd95-a598-40dc-8c9d-2fd63edc6070%40googlegroups.com.