CI/CD Jenkins for Non Java projects

2017-11-01 Thread samy raj 
Hello All,
I am looking for a simple project example which has non-java for a complete 
cycle of DevOps. I have a requirement for a project which has just many 
configuration files, Unix script files. I am able to move them into github. 
But, I need to understand how to build and to write deployment pipeline. 
Before deployment I need to modify those files by updating few 
environmental related variables as it differrs between QA and Prod.  I am 
searched many tutorials all are providing example with java build.You 
advise on my question is much appreciated.

-- 
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/d75cb772-fa53-43b0-802d-6a93421eb450%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Event]: Bugs wanted

2017-11-01 Thread Stephen Connolly 
On 1 November 2017 at 13:30, Alyssa Tong  wrote:

> Hi All,
>
> Out of sheer fun, plus getting a bug fixed, Stephen Connolly
>  has signed up to do a live bug fix at the
> upcoming Jenkins Online Meetup
> , he will
> attempt to do this in 20 minutes.  With that said, I am looking for bug
> suggestions.  Stephen will vet the suggested bugs and pick 1 (one) that he
> will fix.
>

Attempt to fix.

I'm looking for a bug that I think I have about 50% chance of actually
fixing in the time window.

The idea being to share how I tackle the issue of bug fixing rather than
just fixing a bug.

So we want something interesting, but not too interesting... the goldilocks
of bugs if you will!


>
> Pls send me your bug suggestions by this Friday, 3rd Nov 8am PT and plan
> to watch it go down live next Tuesday, 7 Nov @ 8am PT
>
> Thanks,
> alyssa
>
> --
> 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/CAC9wNaxibX7QnMj-vqSnzJ0YXH3G9b96qcGuwP6n%
> 2BQJ3fJuqOQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Is there a way of cloning the repo an additional layer down?

2017-11-01 Thread Mark Waite 
On Wed, Nov 1, 2017 at 2:36 PM itchymuzzle  wrote:

> > If you use the dir('dest-dir') { checkout scm } syntax, you avoid using
> that special case from the git plugin, and have something that is
> maintained in code (and looks like pipeline), rather than something that
> looks like a special case of the git plugin.
>
> This works, but the code is cloned twice.  Once in the workspace, then
> again into the sub directory defined by dir('dest-dir'), in the same
> workspace.  I assume there is no way around this, as Jenkinsfile needs to
> be found, to be able to use it.  But I figured I would ask.  Thanks.
>

If you use one of the more advanced branch sources (GitHub or Gitea or
possibly Bitbucket), I believe they use a different technique to read the
Jenkinsfile.  That different technique does not require a full clone of the
repository.

Stephen Connolly has a series of "live coding" blog posts which show his
work on the Apache Maven project which may lead to additional ways of
avoiding the full clone to obtain the Jenkinsfile.  Refer to
https://www.cloudbees.com/blog/watch-me-code-episode-1

Mark Waite


> --
> 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/b9acde7c-a050-4b6b-8979-c97a51633959%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [Event]: Bugs wanted

2017-11-01 Thread Daniel Beck 

> On 1. Nov 2017, at 21:30, Alyssa Tong  wrote:
> 
> Pls send me your bug suggestions by this Friday, 3rd Nov 8am PT and plan to 
> watch it go down live next Tuesday, 7 Nov @ 8am PT  
> 

JENKINS-45927
JENKINS-34337
JENKINS-44972
JENKINS-18992 isn't quite a bug, but close to it, given lazy build loading.

-- 
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/7C519D26-AC46-4A02-B990-10A202DD97CF%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Is there a way of cloning the repo an additional layer down?

2017-11-01 Thread itchymuzzle 
> If you use the dir('dest-dir') { checkout scm } syntax, you avoid using 
that special case from the git plugin, and have something that is 
maintained in code (and looks like pipeline), rather than something that 
looks like a special case of the git plugin.

This works, but the code is cloned twice.  Once in the workspace, then 
again into the sub directory defined by dir('dest-dir'), in the same 
workspace.  I assume there is no way around this, as Jenkinsfile needs to 
be found, to be able to use it.  But I figured I would ask.  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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b9acde7c-a050-4b6b-8979-c97a51633959%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Event]: Bugs wanted

2017-11-01 Thread Alyssa Tong 
Hi All,

Out of sheer fun, plus getting a bug fixed, Stephen Connolly
 has signed up to do a live bug fix at the
upcoming Jenkins Online Meetup
, he will
attempt to do this in 20 minutes.  With that said, I am looking for bug
suggestions.  Stephen will vet the suggested bugs and pick 1 (one) that he
will fix.

Pls send me your bug suggestions by this Friday, 3rd Nov 8am PT and plan to
watch it go down live next Tuesday, 7 Nov @ 8am PT

Thanks,
alyssa

-- 
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/CAC9wNaxibX7QnMj-vqSnzJ0YXH3G9b96qcGuwP6n%2BQJ3fJuqOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hard] problem building github tags

2017-11-01 Thread j . knurek 
hmm, I checked out your branch:
https://github.com/stephenc/github-branch-source-plugin/tree/jenkins-34395
compiled and installed: 2.2.5-SNAPSHOT (private-e98acfa4-root)
but still not seeing any tags built



On Wednesday, 1 November 2017 16:54:22 UTC+1, Stephen Connolly wrote:
>
> 2.2.4 does not have discovery of tags merged yet
>
> On 1 November 2017 at 08:15,  
> wrote:
>
>> I've got version 2.2.4 of GitHub Branch Source Plugin installed, and
>> compiled, installed, and configured my organization folder to use 
>> https://github.com/AngryBytes/jenkins-build-everything-strategy-plugin
>> which uses:
>>  @Override
>> public boolean isAutomaticBuild(SCMSource source, SCMHead head) {
>> return true;
>> }
>>
>> then I run a Scan the organization folder, but don't see any mention to 
>> the tags. What's up with that? Is there something else missing along the 
>> way?
>>
>> Examining org/repo
>>
>>   Checking branches...
>>
>>   Getting remote branches...
>>
>> Checking branch feature/publishers
>>   ‘Jenkinsfile’ found
>> Met criteria
>> No changes detected: feature/publishers (still at 
>> a29373c2e692bf549f7ff114e4be6ed82f7d056d)
>>
>> Checking branch master
>>   ‘Jenkinsfile’ found
>> Met criteria
>> No changes detected: master (still at 
>> a9bc55ee5d6e82111f6ca70ea6168da9289ddd12)
>>
>> Checking branch test
>>   ‘Jenkinsfile’ found
>> Met criteria
>> No changes detected: test (still at 
>> b224b0276df138020efed0d1545f97c4bff294cd)
>>
>>   3 branches were processed
>>
>>   Checking pull-requests...
>>
>>   Getting remote pull requests...
>>
>>   0 pull requests were processed
>>
>> Finished examining org/repo
>>
>>
>>
>>
>> On Thursday, 7 September 2017 11:43:41 UTC+2, Stephen Connolly wrote:
>>>
>>>
>>>
>>> On 6 September 2017 at 23:24, Stephen Connolly  
>>> wrote:
>>>

 On Thu 7 Sep 2017 at 07:22, Stephen Connolly  
 wrote:

> You are waiting on 
> https://github.com/jenkinsci/github-branch-source-plugin/pull/158 to 
> be merged then.
>
> You could build the plugin with the PR merged and do some testing to 
> help give better confidence for releasing that PR
>
>
> On Thu 7 Sep 2017 at 00:43,  wrote:
>
>> Oh, to clarify, we're using the "github branch source" plugin and I 
>> have already confirmed that github is correctly firing the webhook.
>>
>
 Hmmm the event side of that PR may need updating... 

 Would be really good to see if tags get created by events or if they 
 only show on an index with the current PR

>>>
>>> Had a look at the code, tag events were not being handled, so I pushed 
>>> https://github.com/jenkinsci/github-branch-source-plugin/pull/158/commits/51fc6efbfed92f541032ed672be2ee9d9ac2e398
>>>  
>>> which should provide event support for tags
>>>
>>> Now if you want tags to build automatically, then you will need to write 
>>> an extension plugin for branch-api that provides an implementation of 
>>> https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/BranchBuildStrategy.java
>>>  
>>> (one there is at least one BranchBuildStrategy extension defined in your 
>>> Jenkins then the BranchSource should allow you to add the strategies: 
>>> https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/resources/jenkins/branch/BranchSource/config.jelly#L45
>>>  
>>> Note though, 
>>> https://github.com/jenkinsci/branch-api-plugin/blob/22c8d12a5ad3b523042343bb769b15affb11d1a6/src/main/java/jenkins/branch/MultiBranchProject.java#L2162-L2173
>>>  
>>> so if you configure a source with one or more BranchBuildStrategy instances 
>>> then that source will stop using the default behaviour of auto-build 
>>> anything that is not a tag, so you might need more than one strategy to 
>>> provide the flexibility you want
>>>  
>>>


>>
>> On Wednesday, September 6, 2017 at 4:38:05 PM UTC-7, 
>> aham...@anchorfree.com wrote:
>>>
>>> One of the fundamental concepts in CI/CD is "build once". So... we 
>>> build for every commit and test. Code which we want to promote, we 
>>> merge 
>>> and then test again. If tests pass, we tag it with a release number in 
>>> git 
>>> (v3.2 for example) and push that. I expect jenkins to fire a build. Our 
>>> jenkinsfile will then do a docker pull and discover it's already built, 
>>> apply the new tag and docker push.
>>>
>>> But it sounds like this workflow is fundamentally not possible with 
>>> Jenkins. Is that correct?
>>>
>>> A
>>>
>>> On Friday, July 14, 2017 at 9:00:10 AM UTC-7, Mark Waite wrote:



 On Friday, July 14, 2017 at 7:56:00 AM UTC-8, Samuel Henrique wrote:
>
> Hello,
>
> I'm trying to make jenkins trigger a build

Re: [hard] problem building github tags

2017-11-01 Thread j . knurek 
ah, well that explains it :)

I should have paid more attention that the PR is still open 
https://github.com/jenkinsci/github-branch-source-plugin/pull/158/


On Wednesday, 1 November 2017 16:54:22 UTC+1, Stephen Connolly wrote:
>
> 2.2.4 does not have discovery of tags merged yet
>
> On 1 November 2017 at 08:15,  
> wrote:
>
>> I've got version 2.2.4 of GitHub Branch Source Plugin installed, and
>> compiled, installed, and configured my organization folder to use 
>> https://github.com/AngryBytes/jenkins-build-everything-strategy-plugin
>> which uses:
>>  @Override
>> public boolean isAutomaticBuild(SCMSource source, SCMHead head) {
>> return true;
>> }
>>
>> then I run a Scan the organization folder, but don't see any mention to 
>> the tags. What's up with that? Is there something else missing along the 
>> way?
>>
>> Examining org/repo
>>
>>   Checking branches...
>>
>>   Getting remote branches...
>>
>> Checking branch feature/publishers
>>   ‘Jenkinsfile’ found
>> Met criteria
>> No changes detected: feature/publishers (still at 
>> a29373c2e692bf549f7ff114e4be6ed82f7d056d)
>>
>> Checking branch master
>>   ‘Jenkinsfile’ found
>> Met criteria
>> No changes detected: master (still at 
>> a9bc55ee5d6e82111f6ca70ea6168da9289ddd12)
>>
>> Checking branch test
>>   ‘Jenkinsfile’ found
>> Met criteria
>> No changes detected: test (still at 
>> b224b0276df138020efed0d1545f97c4bff294cd)
>>
>>   3 branches were processed
>>
>>   Checking pull-requests...
>>
>>   Getting remote pull requests...
>>
>>   0 pull requests were processed
>>
>> Finished examining org/repo
>>
>>
>>
>>
>> On Thursday, 7 September 2017 11:43:41 UTC+2, Stephen Connolly wrote:
>>>
>>>
>>>
>>> On 6 September 2017 at 23:24, Stephen Connolly  
>>> wrote:
>>>

 On Thu 7 Sep 2017 at 07:22, Stephen Connolly  
 wrote:

> You are waiting on 
> https://github.com/jenkinsci/github-branch-source-plugin/pull/158 to 
> be merged then.
>
> You could build the plugin with the PR merged and do some testing to 
> help give better confidence for releasing that PR
>
>
> On Thu 7 Sep 2017 at 00:43,  wrote:
>
>> Oh, to clarify, we're using the "github branch source" plugin and I 
>> have already confirmed that github is correctly firing the webhook.
>>
>
 Hmmm the event side of that PR may need updating... 

 Would be really good to see if tags get created by events or if they 
 only show on an index with the current PR

>>>
>>> Had a look at the code, tag events were not being handled, so I pushed 
>>> https://github.com/jenkinsci/github-branch-source-plugin/pull/158/commits/51fc6efbfed92f541032ed672be2ee9d9ac2e398
>>>  
>>> which should provide event support for tags
>>>
>>> Now if you want tags to build automatically, then you will need to write 
>>> an extension plugin for branch-api that provides an implementation of 
>>> https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/BranchBuildStrategy.java
>>>  
>>> (one there is at least one BranchBuildStrategy extension defined in your 
>>> Jenkins then the BranchSource should allow you to add the strategies: 
>>> https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/resources/jenkins/branch/BranchSource/config.jelly#L45
>>>  
>>> Note though, 
>>> https://github.com/jenkinsci/branch-api-plugin/blob/22c8d12a5ad3b523042343bb769b15affb11d1a6/src/main/java/jenkins/branch/MultiBranchProject.java#L2162-L2173
>>>  
>>> so if you configure a source with one or more BranchBuildStrategy instances 
>>> then that source will stop using the default behaviour of auto-build 
>>> anything that is not a tag, so you might need more than one strategy to 
>>> provide the flexibility you want
>>>  
>>>


>>
>> On Wednesday, September 6, 2017 at 4:38:05 PM UTC-7, 
>> aham...@anchorfree.com wrote:
>>>
>>> One of the fundamental concepts in CI/CD is "build once". So... we 
>>> build for every commit and test. Code which we want to promote, we 
>>> merge 
>>> and then test again. If tests pass, we tag it with a release number in 
>>> git 
>>> (v3.2 for example) and push that. I expect jenkins to fire a build. Our 
>>> jenkinsfile will then do a docker pull and discover it's already built, 
>>> apply the new tag and docker push.
>>>
>>> But it sounds like this workflow is fundamentally not possible with 
>>> Jenkins. Is that correct?
>>>
>>> A
>>>
>>> On Friday, July 14, 2017 at 9:00:10 AM UTC-7, Mark Waite wrote:



 On Friday, July 14, 2017 at 7:56:00 AM UTC-8, Samuel Henrique wrote:
>
> Hello,
>
> I'm trying to make jenkins trigger a build whenever a new tag is 
> pushed to my git

Re: [hard] problem building github tags

2017-11-01 Thread Stephen Connolly 
2.2.4 does not have discovery of tags merged yet

On 1 November 2017 at 08:15,  wrote:

> I've got version 2.2.4 of GitHub Branch Source Plugin installed, and
> compiled, installed, and configured my organization folder to use
> https://github.com/AngryBytes/jenkins-build-everything-strategy-plugin
> which uses:
>  @Override
> public boolean isAutomaticBuild(SCMSource source, SCMHead head) {
> return true;
> }
>
> then I run a Scan the organization folder, but don't see any mention to
> the tags. What's up with that? Is there something else missing along the
> way?
>
> Examining org/repo
>
>   Checking branches...
>
>   Getting remote branches...
>
> Checking branch feature/publishers
>   ‘Jenkinsfile’ found
> Met criteria
> No changes detected: feature/publishers (still at
> a29373c2e692bf549f7ff114e4be6ed82f7d056d)
>
> Checking branch master
>   ‘Jenkinsfile’ found
> Met criteria
> No changes detected: master (still at a9bc55ee5d6e82111f6ca70ea6168d
> a9289ddd12)
>
> Checking branch test
>   ‘Jenkinsfile’ found
> Met criteria
> No changes detected: test (still at b224b0276df138020efed0d1545f97
> c4bff294cd)
>
>   3 branches were processed
>
>   Checking pull-requests...
>
>   Getting remote pull requests...
>
>   0 pull requests were processed
>
> Finished examining org/repo
>
>
>
>
> On Thursday, 7 September 2017 11:43:41 UTC+2, Stephen Connolly wrote:
>>
>>
>>
>> On 6 September 2017 at 23:24, Stephen Connolly 
>> wrote:
>>
>>>
>>> On Thu 7 Sep 2017 at 07:22, Stephen Connolly 
>>> wrote:
>>>
 You are waiting on https://github.com/jenkinsc
 i/github-branch-source-plugin/pull/158 to be merged then.

 You could build the plugin with the PR merged and do some testing to
 help give better confidence for releasing that PR


 On Thu 7 Sep 2017 at 00:43,  wrote:

> Oh, to clarify, we're using the "github branch source" plugin and I
> have already confirmed that github is correctly firing the webhook.
>

>>> Hmmm the event side of that PR may need updating...
>>>
>>> Would be really good to see if tags get created by events or if they
>>> only show on an index with the current PR
>>>
>>
>> Had a look at the code, tag events were not being handled, so I pushed
>> https://github.com/jenkinsci/github-branch-source-plugin/pul
>> l/158/commits/51fc6efbfed92f541032ed672be2ee9d9ac2e398 which should
>> provide event support for tags
>>
>> Now if you want tags to build automatically, then you will need to write
>> an extension plugin for branch-api that provides an implementation of
>> https://github.com/jenkinsci/branch-api-plugin/blob/master/s
>> rc/main/java/jenkins/branch/BranchBuildStrategy.java (one there is at
>> least one BranchBuildStrategy extension defined in your Jenkins then the
>> BranchSource should allow you to add the strategies: https://github.com
>> /jenkinsci/branch-api-plugin/blob/master/src/main/resources
>> /jenkins/branch/BranchSource/config.jelly#L45 Note though,
>> https://github.com/jenkinsci/branch-api-plugin/blob/
>> 22c8d12a5ad3b523042343bb769b15affb11d1a6/src/main/java/jenki
>> ns/branch/MultiBranchProject.java#L2162-L2173 so if you configure a
>> source with one or more BranchBuildStrategy instances then that source will
>> stop using the default behaviour of auto-build anything that is not a tag,
>> so you might need more than one strategy to provide the flexibility you want
>>
>>
>>>
>>>
>
> On Wednesday, September 6, 2017 at 4:38:05 PM UTC-7,
> aham...@anchorfree.com wrote:
>>
>> One of the fundamental concepts in CI/CD is "build once". So... we
>> build for every commit and test. Code which we want to promote, we merge
>> and then test again. If tests pass, we tag it with a release number in 
>> git
>> (v3.2 for example) and push that. I expect jenkins to fire a build. Our
>> jenkinsfile will then do a docker pull and discover it's already built,
>> apply the new tag and docker push.
>>
>> But it sounds like this workflow is fundamentally not possible with
>> Jenkins. Is that correct?
>>
>> A
>>
>> On Friday, July 14, 2017 at 9:00:10 AM UTC-7, Mark Waite wrote:
>>>
>>>
>>>
>>> On Friday, July 14, 2017 at 7:56:00 AM UTC-8, Samuel Henrique wrote:

 Hello,

 I'm trying to make jenkins trigger a build whenever a new tag is
 pushed to my git repo.

 I already made it to trigger builds when a tag pointing to a new
 commit is pushed, by setting:

 *refspec:* +refs/tags/*:refs/remotes/origin/tags/*
> *branch specifier:* **


 The problem is that the builds are not triggered when i tag some
 commit that already has another tag, even if its an annotated tag.

 The use

Re: Kubernetes Plugin - Add ‘Environment Variable’ Button is not functional in Jenkins ‘Configure System’ under ‘Container Template’

2017-11-01 Thread Carlos Sanchez 
It's a known issue
https://issues.jenkins-ci.org/plugins/servlet/mobile#issue/JENKINS-47112

On Wed, Nov 1, 2017, 16:29 Avi Segev  wrote:

>
>
> Versions used:  Jenkins ver.  2.60.1, Kubernetes plugin version 1.0 (also
> tested on version 1.1).
>
>
> We have a functional dynamically provisioned Jenkins slave that was
> initially configured with a container template and a few environment
> variables.
>
> For some reason the buttons ‘Add Environment Variable’ in the Jenkins
> Configure form (under the ‘Cloud’ section) are no longer functional (the
> button / drop down list is empty)
>
>
>
> *Notes*
>
>
>- The following may be related; we also observed that when the
>‘Jenkins   Configure System’ form is saved there is a server log with the
>following warning:
>
> Nov 01, 2017 12:04:24 AM hudson.model.Descriptor verifyNewInstance
>
> WARNING: Father of ContainerEnvVar [getValue()=xyz, getKey()=kkk] and its
> getDescriptor() points to two different instances. Probably malplaced
> @Extension. See
> http://hudson.361315.n4.nabble.com/Help-Hint-needed-Post-build-action-doesn-t-stay-activated-td2308833.html
>
>
>- The provisioned slave works fine with the existing configured
>environment variables present in the container as expected. The issue that
>we have is adding new Pod Templates with container templates and
>environment variables.
>
>
>
>
>
>
>
>
>
> --
> 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/e7cb8fa7-a7f9-4069-8602-45621c641d94%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [hard] problem building github tags

2017-11-01 Thread j . knurek 
I've got version 2.2.4 of GitHub Branch Source Plugin installed, and
compiled, installed, and configured my organization folder to 
use https://github.com/AngryBytes/jenkins-build-everything-strategy-plugin
which uses:
 @Override
public boolean isAutomaticBuild(SCMSource source, SCMHead head) {
return true;
}

then I run a Scan the organization folder, but don't see any mention to the 
tags. What's up with that? Is there something else missing along the way?

Examining org/repo

  Checking branches...

  Getting remote branches...

Checking branch feature/publishers
  ‘Jenkinsfile’ found
Met criteria
No changes detected: feature/publishers (still at 
a29373c2e692bf549f7ff114e4be6ed82f7d056d)

Checking branch master
  ‘Jenkinsfile’ found
Met criteria
No changes detected: master (still at 
a9bc55ee5d6e82111f6ca70ea6168da9289ddd12)

Checking branch test
  ‘Jenkinsfile’ found
Met criteria
No changes detected: test (still at 
b224b0276df138020efed0d1545f97c4bff294cd)

  3 branches were processed

  Checking pull-requests...

  Getting remote pull requests...

  0 pull requests were processed

Finished examining org/repo




On Thursday, 7 September 2017 11:43:41 UTC+2, Stephen Connolly wrote:
>
>
>
> On 6 September 2017 at 23:24, Stephen Connolly  > wrote:
>
>>
>> On Thu 7 Sep 2017 at 07:22, Stephen Connolly > > wrote:
>>
>>> You are waiting on 
>>> https://github.com/jenkinsci/github-branch-source-plugin/pull/158 to be 
>>> merged then.
>>>
>>> You could build the plugin with the PR merged and do some testing to 
>>> help give better confidence for releasing that PR
>>>
>>>
>>> On Thu 7 Sep 2017 at 00:43,  
>>> wrote:
>>>
 Oh, to clarify, we're using the "github branch source" plugin and I 
 have already confirmed that github is correctly firing the webhook.

>>>
>> Hmmm the event side of that PR may need updating... 
>>
>> Would be really good to see if tags get created by events or if they only 
>> show on an index with the current PR
>>
>
> Had a look at the code, tag events were not being handled, so I pushed 
> https://github.com/jenkinsci/github-branch-source-plugin/pull/158/commits/51fc6efbfed92f541032ed672be2ee9d9ac2e398
>  
> which should provide event support for tags
>
> Now if you want tags to build automatically, then you will need to write 
> an extension plugin for branch-api that provides an implementation of 
> https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/BranchBuildStrategy.java
>  
> (one there is at least one BranchBuildStrategy extension defined in your 
> Jenkins then the BranchSource should allow you to add the strategies: 
> https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/resources/jenkins/branch/BranchSource/config.jelly#L45
>  
> Note though, 
> https://github.com/jenkinsci/branch-api-plugin/blob/22c8d12a5ad3b523042343bb769b15affb11d1a6/src/main/java/jenkins/branch/MultiBranchProject.java#L2162-L2173
>  
> so if you configure a source with one or more BranchBuildStrategy instances 
> then that source will stop using the default behaviour of auto-build 
> anything that is not a tag, so you might need more than one strategy to 
> provide the flexibility you want
>  
>
>>
>>

 On Wednesday, September 6, 2017 at 4:38:05 PM UTC-7, 
 aham...@anchorfree.com wrote:
>
> One of the fundamental concepts in CI/CD is "build once". So... we 
> build for every commit and test. Code which we want to promote, we merge 
> and then test again. If tests pass, we tag it with a release number in 
> git 
> (v3.2 for example) and push that. I expect jenkins to fire a build. Our 
> jenkinsfile will then do a docker pull and discover it's already built, 
> apply the new tag and docker push.
>
> But it sounds like this workflow is fundamentally not possible with 
> Jenkins. Is that correct?
>
> A
>
> On Friday, July 14, 2017 at 9:00:10 AM UTC-7, Mark Waite wrote:
>>
>>
>>
>> On Friday, July 14, 2017 at 7:56:00 AM UTC-8, Samuel Henrique wrote:
>>>
>>> Hello,
>>>
>>> I'm trying to make jenkins trigger a build whenever a new tag is 
>>> pushed to my git repo.
>>>
>>> I already made it to trigger builds when a tag pointing to a new 
>>> commit is pushed, by setting:
>>>
>>> *refspec:* +refs/tags/*:refs/remotes/origin/tags/*
 *branch specifier:* **
>>>
>>>
>>> The problem is that the builds are not triggered when i tag some 
>>> commit that already has another tag, even if its an annotated tag.
>>>
>>> The use case is as follows:
>>>
>>> 1)We need devs to be able to deploy our webapp by tagging releases 
>>> on github (mostly in other branches than master), like tag: v1.0.0 (the 
>>> previous tag was v0.9.9).
>>> 2)We need to be

Re: Best way to develop pipeline groovy

2017-11-01 Thread Christoph Ruepprich 
Thanks Daniel,
when making changes in replay, is there a way to promote those changes to 
the actual script, or would I have to copy them?

Will the Jenkins CLI work only for declarative pipeline syntax, or will 
scripts work, too?

Cheers,
C

On Wednesday, 1 November 2017 08:02:12 UTC-5, Daniel Beck wrote:
>
>
> > On 31. Oct 2017, at 22:51, Christoph Ruepprich  > wrote: 
> > 
> > This gets pretty tedious and time consuming. Is there a better way to 
> develop scripts without having to either develop them in the web UI or copy 
> & paste them? 
>
> https://jenkins.io/blog/2016/04/14/replay-with-pipeline might also help. 
>
> The declarative pipeline syntax also has a linter accessible from the 
> Jenkins CLI, which should cut down on the trial & error executions: 
> https://jenkins.io/doc/book/pipeline/development/#linter 
>
>

-- 
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/30c0e3a4-aece-4398-9351-fe21d0f886bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Best way to develop pipeline groovy

2017-11-01 Thread Christoph Ruepprich 
Thanks Alex,
I think the replay is probably the better option for me.

C

On Tuesday, 31 October 2017 17:05:14 UTC-5, slide wrote:
>
> There are two things that might make your life easier:
>
> 1) Jenkinsfile, you can put this into your source control and then it will 
> be executed as if it were in the web ui. You just change the option in the 
> job setup to "Pipeline script from SCM" instead of "Pipeline script". Then 
> when you push updates to the Jenkinsfile, it will use your changes.
> 2) The Replay. This allows you to rerun a pipeline job and make small 
> modifications to the script that was used to test things out, then you can 
> incorporate those changes into your Jenkinsfile.
>
> Hope those things help
>
> Alex
>
> On Tue, Oct 31, 2017 at 2:51 PM Christoph Ruepprich  > wrote:
>
>> I'm new to Jenkins and am learning how to write groovy scripts for 
>> pipelines. Right now I write my code in VS Code and copy & paste it into 
>> the Jenkins' project, save and build. This gets pretty tedious and time 
>> consuming. Is there a better way to develop scripts without having to 
>> either develop them in the web UI or copy & paste them?
>>
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/a2f17740-5fec-4b9b-977c-df877bdf0fbc%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

Kubernetes Plugin - Add ‘Environment Variable’ Button is not functional in Jenkins ‘Configure System’ under ‘Container Template’

2017-11-01 Thread Avi Segev 


 

Versions used:  Jenkins ver.  2.60.1, Kubernetes plugin version 1.0 (also 
tested on version 1.1).


We have a functional dynamically provisioned Jenkins slave that was 
initially configured with a container template and a few environment 
variables.

For some reason the buttons ‘Add Environment Variable’ in the Jenkins 
Configure form (under the ‘Cloud’ section) are no longer functional (the 
button / drop down list is empty)

 

*Notes*


   - The following may be related; we also observed that when the ‘Jenkins 
 Configure System’ form is saved there is a server log with the following 
   warning:
   
Nov 01, 2017 12:04:24 AM hudson.model.Descriptor verifyNewInstance

WARNING: Father of ContainerEnvVar [getValue()=xyz, getKey()=kkk] and its 
getDescriptor() points to two different instances. Probably malplaced 
@Extension. See 
http://hudson.361315.n4.nabble.com/Help-Hint-needed-Post-build-action-doesn-t-stay-activated-td2308833.html


   - The provisioned slave works fine with the existing configured 
   environment variables present in the container as expected. The issue that 
   we have is adding new Pod Templates with container templates and 
   environment variables.
   
 

 

 

 

-- 
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/e7cb8fa7-a7f9-4069-8602-45621c641d94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Uninstall jenkins and its dependencies from Red Hat Linux Enterprise Edition(5.8)

2017-11-01 Thread yerriswamy . konanki 
Hi,

You can try the following command "sudo yum remove jenkins"


On Thursday, October 13, 2016 at 1:47:15 PM UTC+5:30, chinmoy padhi wrote:
>
> Hi Google Users,
>
> I am trying to uninstall jenkins using rpm -e commands, but it is not at 
> all removing all the dependencies.
> So how to uninstall, so that all dependencies can be removed? Currently I 
> am trying to do the same on Red Hat Linux Enterprise Edition (5.8)
>
> Appreciate your help
>
> Thanks,
> Chinmoy
>

-- 
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/54bb7b58-d2ad-4263-ab9d-15bded7acfe3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Best way to develop pipeline groovy

2017-11-01 Thread Daniel Beck 

> On 31. Oct 2017, at 22:51, Christoph Ruepprich  wrote:
> 
> This gets pretty tedious and time consuming. Is there a better way to develop 
> scripts without having to either develop them in the web UI or copy & paste 
> them?

https://jenkins.io/blog/2016/04/14/replay-with-pipeline might also help.

The declarative pipeline syntax also has a linter accessible from the Jenkins 
CLI, which should cut down on the trial & error executions:
https://jenkins.io/doc/book/pipeline/development/#linter

-- 
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/414FE298-83C0-47CC-B07A-0B58231BADEB%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.