Re: Declarative pipelien DOA after upgrading to 1.3.5 (from 1.3.4.1)

[Mark Waite]

I've been running those versions of declarative pipeline plugins on my
Jenkins instance without any issues.  However, I'm not pulling docker
images from shell steps in my pipeline.

Since the message shows that the failure is inside an 'sh' step, I suspect
there is some infrastructure change that is now denying you access to
Dockerhub.  I don't think that the pipeline plugins know very much about
what's inside an 'sh' step.  Did I read it correctly that the 'docker pull'
is being performed inside an 'sh' step?

However, you indicated that if you downgrade to Docker plugins 1.3.4.1 the
problem disappears.  That indicates the problem is more likely in one of
the upgraded plugins.

Mark Waite

On Tue, Mar 5, 2019 at 4:44 PM Dan Tran  wrote:

>
> all my Jenkins masters facing this issue.  Sounds very serious but so far
> have not heard any complaints yet from external Jenkins users :(
>
> -D
>
> On Monday, March 4, 2019 at 11:02:04 PM UTC-8, Dan Tran wrote:
>>
>>
>>
>> My declarative pipeline errors out with
>>
>> [Pipeline] sh 
>> <https://danlinux.lss.emc.com/job/ecdm/job/ansible/job/ecdm-ansible/196/console#>+
>>  docker pull :
>>
>> Error response from daemon: pull access denied for xxx/yyy, repository does 
>> not exist or may require 'docker login'
>>
>>
>> Wonder if this is a known issue, or just me?
>>
>>
>> Reverting the below plugins fixes the problem
>>
>>
>> Thanks
>>
>>
>> -D
>>
>>
>> Pipeline: Declarative <https://plugins.jenkins.io/pipeline-model-definition>
>> An opinionated, declarative Pipeline.
>> 1.3.5 1.3.4.1
>>
>> Pipeline: Declarative Extension Points API 
>> <https://plugins.jenkins.io/pipeline-model-extensions>
>> APIs for extension points used in Declarative Pipelines.
>> 1.3.5 1.3.4.1
>>
>> Pipeline: Model API <https://plugins.jenkins.io/pipeline-model-api>
>> Model API for Declarative Pipeline.
>> 1.3.5 1.3.4.1
>>
>> Pipeline: Stage Tags Metadata 
>> <https://plugins.jenkins.io/pipeline-stage-tags-metadata>
>> Library plugin for Pipeline stage tag metadata.
>> 1.3.5 1.3.4.1
>>
>>
>>
>>
>> --
> 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/551bb008-f91a-45b9-970d-d423b5e5c0a9%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/551bb008-f91a-45b9-970d-d423b5e5c0a9%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEGu2hzo_r_%2B5e8WZN1h6fhdTDZfYe10kfhwsprKM%3DitQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Class paths for Jenkins?

[Mark Waite]

It seems like you may be trying to extend the functionality of Jenkins with
additional Java code that you want to run inside the Jenkins process on the
Jenkins master, and possibly on one or more agents attached to the master.

If so, first be certain that there isn't already a Jenkins plugin that
solves the specific problem you're trying to solve.  The most frequent
answer to the question, "Do I need to write a plugin to do X?" is "No,
because a plugin already exists to do X, or to do Y which is very similar
to X and can be extended or modified to do X".

If a search of available plugins and a discussion of the specific problem
you're trying to solve does not identify an existing plugin that will meet
the need, then you probably need to write a plugin.

While revising a Jenkins Plugin Development course prior to Jenkins World
2017, I wrote a blog post pointing to many resources on writing Jenkins
plugins.  Refer to
https://jenkins.io/blog/2017/08/07/intro-to-plugin-development/ for that
blog post.

Thanks,
Mark Waite

On Tue, Mar 12, 2019 at 12:10 PM Peter Berghold 
wrote:

> Following up on a silly question from the other day I have another silly
> question. Where does Jenkins look for jar files to resolve classes and
> packages?
>
> I've started writing a Java library that I want to access from a pipeline
> and Jenkins can't seem to find it in spite of it being deployed to
> /usr/share/java where other Java applications find their jars.
>
> Any pointers are appreciated.
>
> --
>
> Peter L. Berghold   salty.cowd...@gmail.com
>
> http://devops.berghold.net
>
>
> --
> 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/CAArvnv2yA6SgjeCyNMmN0v_ecLPCtQgZ2qgu4E2K95B0hd4xqw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAArvnv2yA6SgjeCyNMmN0v_ecLPCtQgZ2qgu4E2K95B0hd4xqw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHjZY_KjBn2k_0L0Knf1Ri-PNq_D9yUQPmSkLkhYNhyYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Getting "Couldn't find any revision to build" error with git checkout

[Mark Waite]

That indicates command line git could not fit any reference that matches
the branch name or SHA 1 it has been asked to build.  Some possible causes
include:

   - Branch name has been requested that is not being fetched because the
   refspec in the "Advanced" section does not include the desired branch
   - Branch name to be built does not match any branch on the remote (typo
   in the branch name to be built)

Mark Waite

On Sat, Mar 16, 2019 at 10:16 AM t3knoid  wrote:

> I have a new Jenkins server that has not used git for checking out. I
> tried using a simple git checkout, just using a freestyle project. For some
> reason I get a "Getting "Couldn't find any revision to build" whenever I
> try to check out. Using an older server checks out the same repo just
> fine...also using a new freestyle job.
>
> Using the new server, I checked out something from github, and that worked
> fine. The server I am using is internal. It is using Bitbucket. I don't
> really think that should make a difference.
>
> --
> 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/a70f0c42-f506-4ab0-b11c-42dd990db4d8%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/a70f0c42-f506-4ab0-b11c-42dd990db4d8%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEhL3vmw3%2BPmNAfyoioBcYNyAukYyNNuf5dFTEvKB4G5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Getting "Couldn't find any revision to build" error with git checkout

[Mark Waite]

On Sat, Mar 16, 2019 at 1:47 PM t3knoid  wrote:

> Thanks for your response.
>
> > Branch name has been requested that is not being fetched because the
> refspec in the "Advanced" section does not include the desired branch
>
> I'm not touching the Advanced section at all.
>
> >Branch name to be built does not match any branch on the remote (typo in
> the branch name to be built)
>
> I'm building the master branch. I've checked and double-checked the URL.
> As I said, when I do the same exact thing on a different Jenkins server, it
> works just fine.
>
>
I'm out of ideas.  Submit a bug report with numbered steps that describe
how to duplicate the bug.

Mark Waite


>
> On Saturday, March 16, 2019 at 12:20:52 PM UTC-4, Mark Waite wrote:
>>
>> That indicates command line git could not fit any reference that matches
>> the branch name or SHA 1 it has been asked to build.  Some possible causes
>> include:
>>
>>- Branch name has been requested that is not being fetched because
>>the refspec in the "Advanced" section does not include the desired branch
>>- Branch name to be built does not match any branch on the remote
>>(typo in the branch name to be built)
>>
>> Mark Waite
>>
>> On Sat, Mar 16, 2019 at 10:16 AM t3knoid  wrote:
>>
>>> I have a new Jenkins server that has not used git for checking out. I
>>> tried using a simple git checkout, just using a freestyle project. For some
>>> reason I get a "Getting "Couldn't find any revision to build" whenever I
>>> try to check out. Using an older server checks out the same repo just
>>> fine...also using a new freestyle job.
>>>
>>> Using the new server, I checked out something from github, and that
>>> worked fine. The server I am using is internal. It is using Bitbucket. I
>>> don't really think that should make a difference.
>>>
>>> --
>>> 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/a70f0c42-f506-4ab0-b11c-42dd990db4d8%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/a70f0c42-f506-4ab0-b11c-42dd990db4d8%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> 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/5ade331c-deb8-44d3-8e67-2abb8f64a9ba%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/5ade331c-deb8-44d3-8e67-2abb8f64a9ba%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtH%2Bvx279YNps1%2BJHh81%3DF5qTW_NV%3D%3Dy1LzzTfvYt_D5%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Getting "Couldn't find any revision to build" error with git checkout

[Mark Waite]

You might change into the workspace directory where the revision can't be
found and look at the output of `git branch -a` and `git log`.  There may
be some hint about something missing from the fetch.

On Sat, Mar 16, 2019 at 7:46 PM t3knoid  wrote:

> Thanks for the suggestions anyway.
>
> BTW, I downloaded Github desktop in the Jenkins slave machine and was able
> to clone without a problem.
>
> On Saturday, March 16, 2019 at 4:02:13 PM UTC-4, Mark Waite wrote:
>>
>>
>>
>> On Sat, Mar 16, 2019 at 1:47 PM t3knoid  wrote:
>>
>>> Thanks for your response.
>>>
>>> > Branch name has been requested that is not being fetched because the
>>> refspec in the "Advanced" section does not include the desired branch
>>>
>>> I'm not touching the Advanced section at all.
>>>
>>> >Branch name to be built does not match any branch on the remote (typo
>>> in the branch name to be built)
>>>
>>> I'm building the master branch. I've checked and double-checked the URL.
>>> As I said, when I do the same exact thing on a different Jenkins server, it
>>> works just fine.
>>>
>>>
>> I'm out of ideas.  Submit a bug report with numbered steps that describe
>> how to duplicate the bug.
>>
>> Mark Waite
>>
>>
>>>
>>> On Saturday, March 16, 2019 at 12:20:52 PM UTC-4, Mark Waite wrote:
>>>>
>>>> That indicates command line git could not fit any reference that
>>>> matches the branch name or SHA 1 it has been asked to build.  Some possible
>>>> causes include:
>>>>
>>>>- Branch name has been requested that is not being fetched because
>>>>the refspec in the "Advanced" section does not include the desired 
>>>> branch
>>>>- Branch name to be built does not match any branch on the remote
>>>>(typo in the branch name to be built)
>>>>
>>>> Mark Waite
>>>>
>>>> On Sat, Mar 16, 2019 at 10:16 AM t3knoid  wrote:
>>>>
>>>>> I have a new Jenkins server that has not used git for checking out. I
>>>>> tried using a simple git checkout, just using a freestyle project. For 
>>>>> some
>>>>> reason I get a "Getting "Couldn't find any revision to build" whenever I
>>>>> try to check out. Using an older server checks out the same repo just
>>>>> fine...also using a new freestyle job.
>>>>>
>>>>> Using the new server, I checked out something from github, and that
>>>>> worked fine. The server I am using is internal. It is using Bitbucket. I
>>>>> don't really think that should make a difference.
>>>>>
>>>>> --
>>>>> 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/a70f0c42-f506-4ab0-b11c-42dd990db4d8%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/a70f0c42-f506-4ab0-b11c-42dd990db4d8%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks!
>>>> 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-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/5ade331c-deb8-44d3-8e67-2abb8f64a9ba%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/5ade331c-deb8-44d3-8e67-2abb8f64a9ba%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> 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/8ddd7f9e-9619-400b-b6cf-08edabec8b8e%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/8ddd7f9e-9619-400b-b6cf-08edabec8b8e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHcwh87dAgpfYqT%2B3HtcHrdhG5w01qG0fSUm%3DG%2Ba1Lp1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Getting "Couldn't find any revision to build" error with git checkout

[Mark Waite]

That's a very useful result.  Thanks for discovering it.  Would you be
willing to put a note into the git plugin wiki page describing what you saw
and how to resolve it?

We've had other surprises like that (credentials manager, for example), and
the wiki page has been a good place to put the information until the time
when the plugin finds a better way to prevent the problem or warn users
about the problem.

Mark Waite

On Mon, Mar 18, 2019 at 11:01 AM t3knoid  wrote:

> I figured out why this was happening. It's user error :-). When installing
> git for windows, make sure to use "Use the native Windows Secure Channel
> library" option during installation.
>
>
>
> On Saturday, March 16, 2019 at 12:15:51 PM UTC-4, t3knoid wrote:
>>
>> I have a new Jenkins server that has not used git for checking out. I
>> tried using a simple git checkout, just using a freestyle project. For some
>> reason I get a "Getting "Couldn't find any revision to build" whenever I
>> try to check out. Using an older server checks out the same repo just
>> fine...also using a new freestyle job.
>>
>> Using the new server, I checked out something from github, and that
>> worked fine. The server I am using is internal. It is using Bitbucket. I
>> don't really think that should make a difference.
>>
> --
> 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/5ee800b6-bd9a-4f31-a804-28341b1212db%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/5ee800b6-bd9a-4f31-a804-28341b1212db%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFzsQeHisBvY5bXMaXmGTSd7r2D%2Br93hvSkaCFvK%2BOrbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: unreliable connection between Jenkins master and slaves

[Mark Waite]

Pipeline jobs already have that behavior.  Pipeline durability settings
allow the PIpeline job to continue running on a disconnected agent.

On Tue, Mar 19, 2019 at 8:21 AM  wrote:

> Hi,
>
> I would like to ask whether there is a good solution for scenarios when
> there is a bad connection between master and slaves. I have a problem with
> long duration tasks where they last for long time. If network problem
> happens the task fails. It would be good enough for master to reconnect to
> the slave and fetch the output accumulated in the meantime.
> The network interruption is so long that SSH connection will drop.
> So looking for some kind of screen+detach scenario.
>
> best regards,
>   Matevz Langus
>
> --
> 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/2d0ad876-df0e-42c1-8ae0-d9ea0a0147b4%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/2d0ad876-df0e-42c1-8ae0-d9ea0a0147b4%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtGiLeQeUP9_%2BmPR_wSQvO16h13bNz0mQxyZwaDW6D1w7Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: @Whitelist pipeline from multibranch project or allow out of sandbox

[Mark Waite]

tsecurity.sandbox.groovy.SandboxInterceptor.onNewInstance(SandboxInterceptor.java:170),
>>  org.kohsuke.groovy.sandbox.impl.Checker$3.call(Checker.java:197), 
>> org.kohsuke.groovy.sandbox.impl.Checker.checkedConstructor(Checker.java:202),
>>  
>> com.cloudbees.groovy.cps.sandbox.SandboxInvoker.constructorCall(SandboxInvoker.java:21),
>>  WorkflowScript.run(WorkflowScript:14), ___cps.transform___(Native Method), 
>> com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:96),
>>  
>> com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82),
>>  sun.reflect.GeneratedMethodAccessor148.invoke(Unknown Source), 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43),
>>  java.lang.reflect.Method.invoke(Method.java:498), 
>> com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72),
>>  com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21), 
>> com.cloudbees.groovy.cps.Next.step(Next.java:83), 
>> com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174), 
>> com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163), 
>> org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129),
>>  
>> org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268),
>>  com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163), 
>> org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34),
>>  
>> org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59),
>>  
>> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:136),
>>  
>> org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58),
>>  
>> org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:182),
>>  
>> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332),
>>  
>> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83),
>>  
>> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244),
>>  
>> org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232),
>>  
>> org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64),
>>  java.util.concurrent.FutureTask.run(FutureTask.java:266), 
>> hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131),
>>  
>> jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28),
>>  
>> jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59),
>>  java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511), 
>> java.util.concurrent.FutureTask.run(FutureTask.java:266), 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149),
>>  
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624),
>>  java.lang.Thread.run(Thread.java:748)]
>>
>> Any ideas how to fix this. what is the right way of targeting this kind
>> of issue?
>> 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/ec75388f-8a03-424f-a9ca-43fd1d9ba452%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/ec75388f-8a03-424f-a9ca-43fd1d9ba452%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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/CADgiF9JDdznaJaQ3wP%2BRA8_YXRcc%3DMq_JtXNU6R56OBUKSFaLg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CADgiF9JDdznaJaQ3wP%2BRA8_YXRcc%3DMq_JtXNU6R56OBUKSFaLg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEEgQ1gS5%3DmvP79YDcpUY2w-n0VEUSpc-9dy_LpFc01wQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: @Whitelist pipeline from multibranch project or allow out of sandbox

[Mark Waite]

On Thu, Mar 21, 2019 at 3:01 AM Guybrush Threepwood 
wrote:

>
> Thank you for your answer,
> I will try that Actually I'm not trying to only delete the directory but
> to create/clean it up.
>
> I was using the File just beacuseI might have landed to the wrong google
> page :-)
> I'm verry new to Jenkins and pipelines and I always want to do complicated
> things.
>
>
I just realized that your use of the File object hints at a larger
misunderstanding about Jenkins Pipeline and where things execute.  Sorry
that I didn't detect that sooner.

Java and groovy logic inside the Pipeline (like your File() call) executes
on the Jenkins master.  Loops, conditionals, and assignments are executed
on the master.  Steps (like dir, deleteDir, checkout) execute where the
implementation of the specific step defines them to execute.   For example,
the dir, deleteDir, and checkout steps all execute on the agent, while the
stash and unstash steps execute on both the agent and the master.

Thus, your use of the File() call was attempting to create a file on the
master, not on the agent or in the workspace like you hoped it would.

The general guiding principle is to place as much of the pipeline work as
possible inside scripts that are called by the sh step or the bat step or
the powershell step.  The more work that you place in the Pipeline script,
the more likely you are to place undue load on your master that would be
better placed on an agent.  Adding more agents for additional capacity is
easy.  Adding more compute capacity to a master is more difficult.

Refer to the free Jenkins Pipeline Fundamentals class
<https://standard.cbu.cloudbees.com/cloudbees-university-jenkins-pipeline-fundamentals>
from CloudBees for more information.  CloudBees also hosts a Pipeline Tips
from the Pros webinar that specifically notes the importance of keeping
Pipeline code as simple as possible, with as much work done in your own
build scripts as you can.


> I agree that whitelisting all the methods probably is not a good Idea.
> And that leads me to two questions.
>
> Why a person is not allowed to do anything in his workspace?
>  is the workspace shared by several executions or it is created each
> time a pipeline is executed.
>
>
The workspace is used for a single execution.  If it does not exist, it is
created.  If it exists and is not in use, it is reused.  If an existing
workspace is already in use, then a new workspace is created for a new
build.


> Why there is no sandbox check for multibranch pipelines as it is for
> regular ones.
>

I don't understand the question.  Can you provide more detail?


> In this case yes I am the Jenkins admin and I know that multi-Branch
> pipeline where is it conected to.
> So if I have the control of the code It would be nice to allow it to run I
> mean I might want to create some admin utilities an put them there
> knowing that they will only run because they are on that multi branch
> pipeline that I can control and users still can not execute nasty things.
>

You may find the blog post from Tyler Croy helpful -
https://brokenco.de/2017/08/03/donut-disable-groovy-sandbox.html


>
> Thank you.
> Thoughts to my two intriguing questions are wellcome.
>
>
>
> El jueves, 21 de marzo de 2019, 5:31:24 (UTC+1), Mark Waite escribió:
>>
>> I don't think it is safe to whitelist the java File object or its methods.
>>
>> Is there a reason you're not relying on the ability of the dir step to
>> create a directory if one does not exist?  Refer to
>> https://stackoverflow.com/questions/42654875/jenkins-pipeline-create-directory
>> for the stackoverflow comments.
>>
>> I wrote the following small test that seems to create a directory, add
>> contents, then remove the directory, using the DSL rather than using java
>> File methods.
>>
>> node('!windows') {
>> echo 'entering'
>> sh 'ls -alrR'
>> echo 'deleting contents'
>> deleteDir()
>> echo 'after content delete'
>> sh 'ls -alrR'
>> dir('some-dir') {
>>sh 'date >> datefile'
>> }
>> echo 'after content create'
>> sh 'ls -alrR'
>> }
>>
>> On Wed, Mar 20, 2019 at 8:24 PM Jan Monterrubio 
>> wrote:
>>
>>> There’s an admin view for white listing method calls. If you don’t have
>>> admin access you can’t see it.
>>>
>>> On Wed, Mar 20, 2019 at 14:03 Guybrush Threepwood 
>>> wrote:
>>>
>>>> hello I have a Jenkins fileas part of a multibranch pipeline But I'm
>>>> getting seccurityissues when trying to create a directory 

Re: Tagging code in a pipeline?

[Mark Waite]

Is the repository URL an ssh URL?  If not, then sshagent won't help.  The
ssh agent does not do http or https

On Thu, Mar 21, 2019 at 12:51 PM Robert Nicholson <
robert.nichol...@gmail.com> wrote:

> I am able to tag the code locally but the push with credentials key based
> seems to be an issue.
>
> sshagent([‘credentialsKey]) {
>sh “git push origin master —tags”
> }
>
> this step errors with
>
> fatal: could not read Username for ‘repository hostname’ : No such device
> or address
>
> Prior in my pipeline I have a repository defined using
>
> Pipeline script from SCM where the url is defined with https://……..git
>
> What is the recommended approach to push when using primary/public key
> with git from JenkinsFile pipeline?
>
> --
> 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/D357517D-5BB0-4A3B-9409-F025C01D470B%40gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtGBhRbuWRLrbxuDUZJpORVyikyGff8B5nFCE62c2L9Zjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: @Whitelist pipeline from multibranch project or allow out of sandbox

[Mark Waite]

On Thu, Mar 21, 2019 at 12:20 PM Guybrush Threepwood 
wrote:

> OMG!!!
> Thank your verry much for your answer.
> I definitelly need to go back to the pipelines fundamentals training looks
> like I missed a lot there.
>
> *The general guiding principle is to place as much of the pipeline work as
> possible inside scripts that are called by the sh step or the bat step or
> the powershell step.  The more work that you place in the Pipeline script,
> the more likely you are to place undue load on your master that would be
> better placed on an agent.  Adding more agents for additional capacity is
> easy.  Adding more compute capacity to a master is more difficult.*
>
> That sounds like verry sensible piece of advice I need to think over that.
> as I was thinking on creating complex groovy pipelines for the logic of
> process not in doing shell scripts. althoughtI want the  agents to do the
> work ofcourse.
>
> Regarding the sandbox
> When you have single pipeline with inline code you have a checkbox to
> disable sandbox.
> But as soon as you select get the source code from SCM the checkbox is
> gone and I guess we are sandboxed again.
> That check box is also gone on multibranch projects since they always are
> from SCM sources.
> it will be nice giving the fact that I know that the SCM is reliable and
> secure to be able to generate pipelines out of the sandbox. (for admin
> purposes)
>
>
>
> If we can not get out of the sandbox in pipelines from scm what would be
> the right approach to automate things like.
> create automatically new simple pipelines (with code on scm)
> or create new roles
> or grant roles to users.
> automatically.
>
>
Those seem like the types of tasks you might want to do with system groovy
script or with the Jenkins command line interface.  They seem to be "system
level" operations that are changing the configuration of the Jenkins
server, rather than specific jobs.

Pipeline is a domain specific language based on groovy which is used in the
Jenkinsfile of Pipeline jobs.  System groovy script is not run from
Pipeline jobs, but rather is executed at startup or from the system groovy
console.  Refer to
https://wiki.jenkins.io/display/JENKINS/Jenkins+Script+Console for more
information on system groovy script.

Mark Waite


> I have to automate those things and I was thinking on having a pipeline
> that could be called via api to do the job for me.
> I do not know if creating libraries is the right place for that. since I
> guess any one can call libraries from their pipelines and I do not want
> that.
>
> Thank you verry much for your clarifications.
>
> Sorry for asking silly questions but I'm forced to learn verry fast about
> this.
>
>
>
> El jueves, 21 de marzo de 2019, 17:11:00 (UTC+1), Mark Waite escribió:
>>
>>
>>
>> On Thu, Mar 21, 2019 at 3:01 AM Guybrush Threepwood 
>> wrote:
>>
>>>
>>> Thank you for your answer,
>>> I will try that Actually I'm not trying to only delete the directory but
>>> to create/clean it up.
>>>
>>> I was using the File just beacuseI might have landed to the wrong google
>>> page :-)
>>> I'm verry new to Jenkins and pipelines and I always want to do
>>> complicated things.
>>>
>>>
>> I just realized that your use of the File object hints at a larger
>> misunderstanding about Jenkins Pipeline and where things execute.  Sorry
>> that I didn't detect that sooner.
>>
>> Java and groovy logic inside the Pipeline (like your File() call)
>> executes on the Jenkins master.  Loops, conditionals, and assignments are
>> executed on the master.  Steps (like dir, deleteDir, checkout) execute
>> where the implementation of the specific step defines them to execute.
>>  For example, the dir, deleteDir, and checkout steps all execute on the
>> agent, while the stash and unstash steps execute on both the agent and the
>> master.
>>
>> Thus, your use of the File() call was attempting to create a file on the
>> master, not on the agent or in the workspace like you hoped it would.
>>
>> The general guiding principle is to place as much of the pipeline work as
>> possible inside scripts that are called by the sh step or the bat step or
>> the powershell step.  The more work that you place in the Pipeline script,
>> the more likely you are to place undue load on your master that would be
>> better placed on an agent.  Adding more agents for additional capacity is
>> easy.  Adding more compute capacity to a master is more difficult.
>>
>> Refer to the free Jenkins Pipeline Fundamentals class
>> <https://standard.cbu

Re: Tagging code in a pipeline?

[Mark Waite]

Most git repository providers (GitHub, Bitbucket, Gitlab, Visual Studio,
Gitea, Assembla, Beanstalk,etc.) provide a small UI component that will
allow you to toggle between the https URL to the repository and the ssh URL
to the repository.

For example, the GitHub box looks like this:

[image: image.png]

If your remote repository does not allow ssh access, then it becomes much
more complicated, though it is probably still possible.

Mark Waite

On Fri, Mar 22, 2019 at 8:00 AM Robert Nicholson 
wrote:

> Ok it’s a https: url
>
> So how do you construct the appropriate
>
> ssh command then?
>
> all examples that use withCredentials seems to fail on my side.
>
>
>
> On Mar 21, 2019, at 1:55 PM, Mark Waite  wrote:
>
> Is the repository URL an ssh URL?  If not, then sshagent won't help.  The
> ssh agent does not do http or https
>
> On Thu, Mar 21, 2019 at 12:51 PM Robert Nicholson <
> robert.nichol...@gmail.com> wrote:
>
>> I am able to tag the code locally but the push with credentials key based
>> seems to be an issue.
>>
>> sshagent([‘credentialsKey]) {
>>sh “git push origin master —tags”
>> }
>>
>> this step errors with
>>
>> fatal: could not read Username for ‘repository hostname’ : No such device
>> or address
>>
>> Prior in my pipeline I have a repository defined using
>>
>> Pipeline script from SCM where the url is defined with https://……..git
>> <https://��..git>
>>
>> What is the recommended approach to push when using primary/public key
>> with git from JenkinsFile pipeline?
>>
>> --
>> 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/D357517D-5BB0-4A3B-9409-F025C01D470B%40gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Thanks!
> 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/CAO49JtGBhRbuWRLrbxuDUZJpORVyikyGff8B5nFCE62c2L9Zjg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGBhRbuWRLrbxuDUZJpORVyikyGff8B5nFCE62c2L9Zjg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> 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/7210C022-28A4-42A1-9F93-06EE882AC357%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/7210C022-28A4-42A1-9F93-06EE882AC357%40gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtF2V2c37J-0uvpcPfw9Vx_d_OUyRpk8Z2iZwvvFwi38Fw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Applying Jenkins Upgrades

[Mark Waite]

See the LTS upgrade guides at  https://jenkins.io/doc/upgrade-guide/

I've upgraded directly to the latest without using intermediate upgrades.
If the installation is large or complex or especially risky, then I would
create a backup on another system and test drive the upgrade there.

On Fri, Mar 22, 2019 at 10:11 AM ShanDar  wrote:

> I need to apply Jenkins Upgrades (currently on Ver 2.60.1)
> I have know knowledge of how Jenkins Upgrades
> Do I have to apply all the upgrades incrementally
> or Can I just to the Latest Upgrade and apply that
>
> Any feedback would be greatly 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/e37ca772-b3f8-4172-aa42-78df5acd21b3%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/e37ca772-b3f8-4172-aa42-78df5acd21b3%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtETuNfPgJWbupYRnU9ZgCAugCivDWr0VFfRZSaj6Vqqcg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GIT_SSH having no effect

[Mark Waite]

If the repository URL is http or https, I suspect that command line git
ignores the values of GIT_SSH and GIT_SSH_COMMAND.

If the repository URL is http or https, why not use the solution provided
at https://jenkins.io/doc/pipeline/examples/#push-git-repo (as noted by
Ivan earlier)?

If the repository URL is ssh, why not use the sshagent step instead of
using withCredentials?

On Fri, Mar 22, 2019 at 3:17 PM Robert Nicholson 
wrote:

> When I try to use
>
> withCredentials()
> withEnv(‘GIT_SSH=doesnotexist’])
>  sh ‘git push origin —tags’
>
> For some reason the GIT_SSH seems to have no effect whatever.
>
> The git push doesn’t complain that way I would have expected
>
> But if I use
>
> withEnv(‘PATH=‘])
> sh ‘git push origin —tags’
>
> That does have the intended affect of complaining about
> Git not being found in the path.
>
> Does anybody know why GIT_SSH nor GIT_SSH_COMMAND appear
> not work with git 2.16.2 like I’m trying?
>
> Sent from my iPad
>
> --
> 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/0566D01A-779B-416F-86DF-CDEF500A64D5%40gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHws1t_-ibbUS663RkVxcbNnQRT7ZFky0GVHMgMZ%2B_%3DHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Tagging code in a pipeline?

[Mark Waite]

https://jenkins.io/doc/pipeline/examples/#push-git-repo provides examples 
of ssh and https.

Mark Waite

On Thursday, March 21, 2019 at 12:51:42 PM UTC-6, Robert Nicholson wrote:
>
> I am able to tag the code locally but the push with credentials key based 
> seems to be an issue. 
>
> sshagent([‘credentialsKey]) { 
>sh “git push origin master —tags” 
> } 
>
> this step errors with 
>
> fatal: could not read Username for ‘repository hostname’ : No such device 
> or address 
>
> Prior in my pipeline I have a repository defined using 
>
> Pipeline script from SCM where the url is defined with https://……..git 
>
> What is the recommended approach to push when using primary/public key 
> with git from JenkinsFile pipeline?

-- 
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/6f3e3e18-bfd6-43a6-ace8-b7beb36abb12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Tagging code in a pipeline?

[Mark Waite]

https://jenkins.io/doc/pipeline/examples/#push-git-repo gives an example of 
both https and ssh

On Saturday, March 23, 2019 at 11:20:27 AM UTC-6, Rade Milijasevic wrote:
>
> Can somebody please give an example code for both https:// url and ssh 
> approach.
> thanks 
>
> On Fri, Mar 22, 2019 at 5:11 PM Robert Nicholson  wrote:
>
>> I haven’t tried any ssh: url based approach yet.
>>
>> but the approaches I’ve seen are when you use GIT_SSH etc to inject your 
>> own private key into the ssh that was
>> extracted using withCredentials and written to a tmp folder on disk 
>> temporarily but I see no indication that it’s
>> ever using this key.
>>
>> On Mar 22, 2019, at 12:13 PM, Ivan Fernandez Calvo  wrote:
>>
>> for the https case, there is an example at 
>> https://jenkins.io/doc/pipeline/examples/#push-git-repo
>>
>> El viernes, 22 de marzo de 2019, 15:00:47 (UTC+1), Robert Nicholson 
>> escribió:
>>>
>>> Ok it’s a https: url
>>>
>>> So how do you construct the appropriate 
>>>
>>> ssh command then?
>>>
>>> all examples that use withCredentials seems to fail on my side.
>>>
>>>
>>>
>>> On Mar 21, 2019, at 1:55 PM, Mark Waite  wrote:
>>>
>>> Is the repository URL an ssh URL?  If not, then sshagent won't help.  
>>> The ssh agent does not do http or https
>>>
>>> On Thu, Mar 21, 2019 at 12:51 PM Robert Nicholson  
>>> wrote:
>>>
>>>> I am able to tag the code locally but the push with credentials key 
>>>> based seems to be an issue.
>>>>
>>>> sshagent([‘credentialsKey]) {
>>>>sh “git push origin master —tags”
>>>> }
>>>>
>>>> this step errors with
>>>>
>>>> fatal: could not read Username for ‘repository hostname’ : No such 
>>>> device or address
>>>>
>>>> Prior in my pipeline I have a repository defined using 
>>>>
>>>> Pipeline script from SCM where the url is defined with https://……..git 
>>>> <https://��..git>
>>>>
>>>> What is the recommended approach to push when using primary/public key 
>>>> with git from JenkinsFile pipeline?
>>>>
>>>> -- 
>>>> 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/D357517D-5BB0-4A3B-9409-F025C01D470B%40gmail.com
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>> -- 
>>> Thanks!
>>> 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-use...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGBhRbuWRLrbxuDUZJpORVyikyGff8B5nFCE62c2L9Zjg%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGBhRbuWRLrbxuDUZJpORVyikyGff8B5nFCE62c2L9Zjg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> 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/fdeaee54-5b99-4e05-a1e6-e02b91e9c0b3%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/fdeaee54-5b99-4e05-a1e6-e02b91e9c0b3%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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/24140516-67D1-4F51-A525-539C447319A2%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/24140516-67D1-4F51-A525-539C447319A2%40gmail.com?utm_medium=email&utm_source=footer>
>> .
>> 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/e67b67c5-e7e8-453e-b4f5-aaa3ddca92f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins upgrade from 2.73.3 to 2.138 deleted all views

[Mark Waite]

Are you sure that you've installed the same plugins on the 2.138.4
installation as you had on the 2.73.1 installation?

Have you placed all the files from the 2.73.1 JENKINS_HOME in the 2.138.4
JENKINS_HOME?

Have you read the Jenkins log from the 2.138.4 installation as it starts,
in case there are helpful suggestions in the log?

Mark Waie

On Tue, Mar 26, 2019 at 8:24 AM Roshan Chandekar <
roshan786.chande...@gmail.com> wrote:

> Hi All,
>
> Need help. I am trying to upgrade the jenkins from 2.73.1 to 2.138.4. But
> it deleted all my views and all jobs showing under "All" tab.
>
> please let me know if someone fixed this issue. I tried the upgrade from
> 2.107 and there as well same issue.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/55f94b7f-e5dc-471d-8d56-80f158db572e%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/55f94b7f-e5dc-471d-8d56-80f158db572e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtGN8Z9aO-fxnKL45BtXVJ6Xf17WSkKbF0GMGvwOiHUeNg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins upgrade from 2.73.3 to 2.138 deleted all views

[Mark Waite]

Those warnings seem to indicate that you'll need to update plugins.  When
you update the plugins to latest versions, does that help?

On Tue, Mar 26, 2019 at 10:38 PM Roshan Chandekar <
roshan786.chande...@gmail.com> wrote:

> Hi Mark,
>
> I am really glad after seeing your response to my issue.
>
> I will explain how i am upgrading first. I downloaded the 2.138 war and
> restarted Jenkins. is it correct way to upgrade? OR do i need to first
> upgrade all plugins on top of 2.73 and then download 2.138 war and restart?
> Please correct my Jenkins upgrade process. Till now i was just downloading
> latest war and restarting Jenkins was working.
>
> Regarding issues from log, i can below errors from log.
>
>
> ===
> WARNING: hudson.plugins.view.dashboard.Dashboard in
> file:/scratch/jenkins/plugins/dashboard-view/WEB-INF/lib/dashboard-view.jar
> might be dangerous, so rejecting; see
> https://jenkins.io/redirect/class-filter/
> Mar 26, 2019 10:13:36 AM jenkins.security.ClassFilterImpl
> lambda$isBlacklisted$1
> WARNING: jenkins.plugins.publish_over.BPInstanceConfig in
> file:/scratch/jenkins/plugins/publish-over-ssh/WEB-INF/lib/publish-over-0.18.jar
> might be dangerous, so rejecting; see
> https://jenkins.io/redirect/class-filter/
>
>
>
> WARNING: Build record migration (
> https://jenkins.io/redirect/build-record-migration) is one-way. If you
> need to downgrade Jenkins, run: java -classpath
> "/scratch/jenkins/war/WEB-INF/lib/jenkins-core-2.107.1.jar:/scratch/jenkins/war/WEB-INF/lib/commons-io-2.4.jar:/scratch/jenkins/war/WEB-INF/lib/stapler-1.254.jar:/scratch/jenkins/war/WEB-INF/lib/ant-1.9.2.jar:/scratch/jenkins/war/WEB-INF/lib/commons-lang-2.6.jar"
> jenkins.model.RunIdMigrator "/scratch/jenkins"
> Mar 26, 2019 10:13:37 AM jenkins.model.RunIdMigrator migrate
> INFO: Migrating build records in /scratch/jenkins/jobs/Main-Pipeline
> (old)/builds
> Mar 26, 2019 10:13:37 AM jenkins.model.RunIdMigrator migrate
> INFO: Migrating build records in
> /scratch/jenkins/jobs/Occs-Frontend-Framework-Pipeline/builds
> Mar 26, 2019 10:13:37 AM jenkins.model.RunIdMigrator migrate
> INFO: Migrating build records in /scratch/jenkins/jobs/CC_ServerExtensions
> - main/builds
> Mar 26, 2019 10:13:37 AM
> com.cloudbees.hudson.plugins.folder.views.DefaultFolderViewHolder
> migrateLegacyPrimaryAllViewLocalizedName
> INFO: JENKINS-38606 detected for AllView in
> com.cloudbees.hudson.plugins.folder.Folder@54b34631[Experiments/ExperimentsSharedLib/SeedJobsTest/Main];
> renaming view from All to all
> Mar 26, 2019 10:13:37 AM
> com.cloudbees.hudson.plugins.folder.views.DefaultFolderViewHolder
> migrateLegacyPrimaryAllViewLocalizedName
> INFO: JENKINS-38606 detected for AllView in
> com.cloudbees.hudson.plugins.folder.Folder@7748c014[Experiments/ExperimentsSharedLib/SeedJobsTest/Shelves];
> renaming view from All to all
> Mar 26, 2019 10:13:37 AM
> com.cloudbees.hudson.plugins.folder.views.DefaultFolderViewHolder
> migrateLegacyPrimaryAllViewLocalizedName
> INFO: JENKINS-38606 detected for AllView in
> com.cloudbees.hudson.plugins.folder.Folder@75b3be9[Experiments/ExperimentsSharedLib/SeedJobsTest/Shelves/ShelvedMain];
> renaming view from All to
>
> =
>
> On Tuesday, March 26, 2019 at 7:59:59 PM UTC+5:30, Mark Waite wrote:
>>
>> Are you sure that you've installed the same plugins on the 2.138.4
>> installation as you had on the 2.73.1 installation?
>>
>> Have you placed all the files from the 2.73.1 JENKINS_HOME in the 2.138.4
>> JENKINS_HOME?
>>
>> Have you read the Jenkins log from the 2.138.4 installation as it starts,
>> in case there are helpful suggestions in the log?
>>
>> Mark Waie
>>
>> On Tue, Mar 26, 2019 at 8:24 AM Roshan Chandekar 
>> wrote:
>>
>>> Hi All,
>>>
>>> Need help. I am trying to upgrade the jenkins from 2.73.1 to 2.138.4.
>>> But it deleted all my views and all jobs showing under "All" tab.
>>>
>>> please let me know if someone fixed this issue. I tried the upgrade from
>>> 2.107 and there as well same issue.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-use...@googlegroups.com.
>>> To view this disc

Re: Two builds for PRs

[Mark Waite]

I thought that was an indication that the GitHub branch source is defined
to both create a job for each branch and for each pull request.  I think
you need to reconfigure the job to not build a branch if it has a matching
pull request.

On Thu, Mar 28, 2019 at 5:17 PM Tom Duerr  wrote:

> Jenkin 2.138
> Branch-Source plugin 2.4.2
> SCM=Github Enterprise
> Amazon Linux
>
> Hi,
>
> We've recently started converting from freestyle jobs to
> Jenkinsfile/pipelines.
>
> We're seeing odd behaviors when pull requests(PR) are created directly
> from our
> main repo and not from a fork of the repo. Specifically around
> the git status checks. PRs that are NOT created from a fork result in two
> git checks and 2 full builds being kicked off.
> We see these 2 checks:
>
> continuous-integration/jenkins/branch
> continuous-integration/jenkins/pr-merge
>
> The PRs from the developers fork, cause only 1 check and 1 build.
> continuous-integration/jenkins/pr-merge
>
> Does anyone know how the 2 checks get created?
> Whats the difference between continuous-integration/jenkins/branch and
> continuous-integration/jenkins/pr-merge?
>
> Thanks,
> Tom
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/7c18652a-1938-487a-ab70-a1e652010e5a%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/7c18652a-1938-487a-ab70-a1e652010e5a%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHpRLxjHRhfyRRUWPKaS%2BBX%2BjfTaPNUrochM1kb95Z_EA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Two builds for PRs

[Mark Waite]

It might also work to filter branches based on the branch name at some
level, but that's more complicated that changing the "Discover branches"
setting in the plugin.

Picture looks like this:

[image: image.png]

On Thu, Mar 28, 2019 at 5:22 PM Slide  wrote:

> This would generally be the branch filter parameter wouldn't it? You'd
> want to filter on the pr-* and master braches
>
> On Thu, Mar 28, 2019, 16:20 Mark Waite  wrote:
>
>> I thought that was an indication that the GitHub branch source is defined
>> to both create a job for each branch and for each pull request.  I think
>> you need to reconfigure the job to not build a branch if it has a matching
>> pull request.
>>
>> On Thu, Mar 28, 2019 at 5:17 PM Tom Duerr  wrote:
>>
>>> Jenkin 2.138
>>> Branch-Source plugin 2.4.2
>>> SCM=Github Enterprise
>>> Amazon Linux
>>>
>>> Hi,
>>>
>>> We've recently started converting from freestyle jobs to
>>> Jenkinsfile/pipelines.
>>>
>>> We're seeing odd behaviors when pull requests(PR) are created directly
>>> from our
>>> main repo and not from a fork of the repo. Specifically around
>>> the git status checks. PRs that are NOT created from a fork result in two
>>> git checks and 2 full builds being kicked off.
>>> We see these 2 checks:
>>>
>>> continuous-integration/jenkins/branch
>>> continuous-integration/jenkins/pr-merge
>>>
>>> The PRs from the developers fork, cause only 1 check and 1 build.
>>> continuous-integration/jenkins/pr-merge
>>>
>>> Does anyone know how the 2 checks get created?
>>> Whats the difference between continuous-integration/jenkins/branch and
>>> continuous-integration/jenkins/pr-merge?
>>>
>>> Thanks,
>>> Tom
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/7c18652a-1938-487a-ab70-a1e652010e5a%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/7c18652a-1938-487a-ab70-a1e652010e5a%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> 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/CAO49JtHpRLxjHRhfyRRUWPKaS%2BBX%2BjfTaPNUrochM1kb95Z_EA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHpRLxjHRhfyRRUWPKaS%2BBX%2BjfTaPNUrochM1kb95Z_EA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> 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/CAPiUgVedC-g4Y68FijmNO8S01MStdutbRnoRZOaJWTgs%3DqAFcw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVedC-g4Y68FijmNO8S01MStdutbRnoRZOaJWTgs%3DqAFcw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFDqMewTaGDUc%2BXUbu_vWyZS47f%3DQedryWbDg-VDwWPGw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Two builds for PRs

[Mark Waite]

That's quite surprising, since my PR evaluation for the git client plugin
on my own fork is running with GitHub and is only showing the 'pr-merge'
job.

Is the second job visible when executing in the Jenkins multibranch
folder?  If so, then I'm puzzled, because you're seeing something that I'm
not seeing.

Are you running the most recent versions of the various plugins?

Mark Waite

On Thu, Mar 28, 2019 at 6:06 PM Tom Duerr  wrote:

> Mark,
> I already have the "Exclude branches that are also filed as PRs" set.
> Guess that's part of my confusion.
>
> On Thu, Mar 28, 2019 at 4:58 PM Mark Waite 
> wrote:
>
>> It might also work to filter branches based on the branch name at some
>> level, but that's more complicated that changing the "Discover branches"
>> setting in the plugin.
>>
>> Picture looks like this:
>>
>> [image: image.png]
>>
>> On Thu, Mar 28, 2019 at 5:22 PM Slide  wrote:
>>
>>> This would generally be the branch filter parameter wouldn't it? You'd
>>> want to filter on the pr-* and master braches
>>>
>>> On Thu, Mar 28, 2019, 16:20 Mark Waite 
>>> wrote:
>>>
>>>> I thought that was an indication that the GitHub branch source is
>>>> defined to both create a job for each branch and for each pull request.  I
>>>> think you need to reconfigure the job to not build a branch if it has a
>>>> matching pull request.
>>>>
>>>> On Thu, Mar 28, 2019 at 5:17 PM Tom Duerr  wrote:
>>>>
>>>>> Jenkin 2.138
>>>>> Branch-Source plugin 2.4.2
>>>>> SCM=Github Enterprise
>>>>> Amazon Linux
>>>>>
>>>>> Hi,
>>>>>
>>>>> We've recently started converting from freestyle jobs to
>>>>> Jenkinsfile/pipelines.
>>>>>
>>>>> We're seeing odd behaviors when pull requests(PR) are created directly
>>>>> from our
>>>>> main repo and not from a fork of the repo. Specifically around
>>>>> the git status checks. PRs that are NOT created from a fork result in
>>>>> two
>>>>> git checks and 2 full builds being kicked off.
>>>>> We see these 2 checks:
>>>>>
>>>>> continuous-integration/jenkins/branch
>>>>> continuous-integration/jenkins/pr-merge
>>>>>
>>>>> The PRs from the developers fork, cause only 1 check and 1 build.
>>>>> continuous-integration/jenkins/pr-merge
>>>>>
>>>>> Does anyone know how the 2 checks get created?
>>>>> Whats the difference between continuous-integration/jenkins/branch and
>>>>> continuous-integration/jenkins/pr-merge?
>>>>>
>>>>> Thanks,
>>>>> Tom
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Jenkins Users" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/jenkinsci-users/7c18652a-1938-487a-ab70-a1e652010e5a%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/7c18652a-1938-487a-ab70-a1e652010e5a%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks!
>>>> 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/CAO49JtHpRLxjHRhfyRRUWPKaS%2BBX%2BjfTaPNUrochM1kb95Z_EA%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHpRLxjHRhfyRRUWPKaS%2BBX%2BjfTaPNUrochM1kb95Z_EA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
>>> You received thi

Re: Two builds for PRs

[Mark Waite]

On Thu, Mar 28, 2019 at 6:22 PM Tom Duerr  wrote:

> Mark,
> The issue only happens when the PR is NOT against a fork.  Its been
> difficult to debug since most of our developers
> use their own forks.
>

I think that is the same condition I'm using with the git client plugin
multibranch configuration that I'm using.


> I think I'm behind on most of the Pipeline related plugins except for the
> branch-source plugin. I had attempted a big
> upgrade of plugins last week that ended badly. Going to retry this
> weekend.
>
> What is the "Jenkins multibranch folder" ? I don't think we're actively
> using the multibranch plugin. Its unclear to me if we need
> that plugin or not if we're already using the branch-source plugin. The
> branch-source plugin seems to do everything we need
> to do. I think we will eventually want to use the multibranch plugin to
> provide different behaviors between a dev, qa or master branch.
> Assuming I actually understand how that plugin works.
>
>
I should have been more clear.  If you're using the GitHub branch source
plugin to define the job, then you're creating a multibranch job.  The
multibranch job is represented as a folder which contains one job for each
branch in the repository.  The containing folder is what I called the
"Jenkins multibranch folder".  No other plugin is needed.

Mark Waite

Tom
>
>
>
> On Thu, Mar 28, 2019 at 5:11 PM Mark Waite 
> wrote:
>
>> That's quite surprising, since my PR evaluation for the git client plugin
>> on my own fork is running with GitHub and is only showing the 'pr-merge'
>> job.
>>
>> Is the second job visible when executing in the Jenkins multibranch
>> folder?  If so, then I'm puzzled, because you're seeing something that I'm
>> not seeing.
>>
>> Are you running the most recent versions of the various plugins?
>>
>> Mark Waite
>>
>> On Thu, Mar 28, 2019 at 6:06 PM Tom Duerr  wrote:
>>
>>> Mark,
>>> I already have the "Exclude branches that are also filed as PRs" set.
>>> Guess that's part of my confusion.
>>>
>>> On Thu, Mar 28, 2019 at 4:58 PM Mark Waite 
>>> wrote:
>>>
>>>> It might also work to filter branches based on the branch name at some
>>>> level, but that's more complicated that changing the "Discover branches"
>>>> setting in the plugin.
>>>>
>>>> Picture looks like this:
>>>>
>>>> [image: image.png]
>>>>
>>>> On Thu, Mar 28, 2019 at 5:22 PM Slide  wrote:
>>>>
>>>>> This would generally be the branch filter parameter wouldn't it? You'd
>>>>> want to filter on the pr-* and master braches
>>>>>
>>>>> On Thu, Mar 28, 2019, 16:20 Mark Waite 
>>>>> wrote:
>>>>>
>>>>>> I thought that was an indication that the GitHub branch source is
>>>>>> defined to both create a job for each branch and for each pull request.  
>>>>>> I
>>>>>> think you need to reconfigure the job to not build a branch if it has a
>>>>>> matching pull request.
>>>>>>
>>>>>> On Thu, Mar 28, 2019 at 5:17 PM Tom Duerr 
>>>>>> wrote:
>>>>>>
>>>>>>> Jenkin 2.138
>>>>>>> Branch-Source plugin 2.4.2
>>>>>>> SCM=Github Enterprise
>>>>>>> Amazon Linux
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> We've recently started converting from freestyle jobs to
>>>>>>> Jenkinsfile/pipelines.
>>>>>>>
>>>>>>> We're seeing odd behaviors when pull requests(PR) are created
>>>>>>> directly from our
>>>>>>> main repo and not from a fork of the repo. Specifically around
>>>>>>> the git status checks. PRs that are NOT created from a fork result
>>>>>>> in two
>>>>>>> git checks and 2 full builds being kicked off.
>>>>>>> We see these 2 checks:
>>>>>>>
>>>>>>> continuous-integration/jenkins/branch
>>>>>>> continuous-integration/jenkins/pr-merge
>>>>>>>
>>>>>>> The PRs from the developers fork, cause only 1 check and 1 build.
>>>>>>> continuous-integration/jenkins/pr-merge
>>>>>&

Re: Jenkins with Webdriver falil to launch browser

[Mark Waite]

The common solution is to create one or more agents that have access to the
Windows desktop.  That is usually done by running the agents with JNLP from
a batch file started on desktop login.

On Sun, Mar 31, 2019 at 5:43 AM Andriy Shegera 
wrote:

> Hello
> Gaurang Shah did you fixed this problem with no launch browser thru the
> Jenkins. If yes, can you share a solution, please?
> Thank you so much.
>
> Andriy
>
>
> On Thursday, August 29, 2013 at 5:28:07 AM UTC-7, Eric Pyle wrote:
>>
>> By default, Windows services run under the Local System account, which
>> does not have access to the desktop. JNLP slaves run as the user logged in
>> who starts up JNLP. Likewise, starting from a war file you run as the user
>> who issues the startup command (java -jar jenkins.war).
>>
>> Eric
>>
>> On 8/29/2013 2:52 AM, Gaurang shah wrote:
>>
>> Thanks Roger,
>>
>> For the update, however i figure out what was wrong.
>>
>> Earlier i was starting Jenkins from the war file and everything was
>> working fine.  however after I install it as windows services it stopped
>> working.
>>
>> After searching i realize that i require node to be created where i want
>> my test case to run.  So i create JNLP node and now it works.
>>
>> However it would be really nice, if someone would explain me why i
>> require JNLP node when i have started jenkins as windows services as i
>> didn't require it when it was started as WAR file.
>>
>> Gaurang Shah
>>
>> On Wednesday, 28 August 2013 02:28:59 UTC+5:30, JonathanRRogers wrote:
>>>
>>>
>>>
>>> On Monday, August 26, 2013 5:32:08 AM UTC-4, Gaurang shah wrote:
>>>>
>>>> Hi Guys,
>>>>
>>>> I have configured my maven project with jenkins. This maven project is
>>>> a
>>>> webdriver automation project.
>>>>
>>>> Project works find when i run from the command line, it launches the
>>>> browser
>>>> and then shows that test case has passed.
>>>>
>>>> However when i run the same project thorough jenkins it is not
>>>> launching any
>>>> browser, however test result says that test case passed.  Without any
>>>> stack
>>>> trace or error I am not able to debug it either. Can someone let me
>>>> know
>>>> what could have been wrong.
>>>>
>>>> I am getting following output when I run though jenkins.
>>>> ---
>>>>  T E S T S
>>>> ---
>>>> Running TestSuite
>>>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.356
>>>> sec
>>>>
>>>> Results :
>>>>
>>>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
>>>>
>>>> [JENKINS] Recording test results
>>>> [JENKINS] Archiving C:\Users\gaurang_shah\workspace\MavenTest\pom.xml
>>>> to
>>>> C:\Users\gaurang_shah\.jenkins\jobs\TestNGMavenDemo\modules\gaurang$MavenTest\builds\2013-08-26_14-51-48\archive\gaurang\MavenTest\0.0.1-SNAPSHOT\MavenTest-0.0.1-SNAPSHOT.pom
>>>>
>>>> [INFO]
>>>> 
>>>>
>>>> [INFO] BUILD SUCCESSFUL
>>>> [INFO]
>>>> 
>>>>
>>>> [INFO] Total time: 44 seconds
>>>> [INFO] Finished at: Mon Aug 26 14:52:40 IST 2013
>>>> [INFO] Final Memory: 17M/42M
>>>> [INFO]
>>>> 
>>>>
>>>> Waiting for Jenkins to finish collecting data
>>>> Finished: SUCCESS
>>>>
>>>
>>>  There may be something missing from the environment when running from
>>> Jenkins that keeps the browser from starting. For example, in my setup, I
>>> have to make sure a headless X11 server is running and the Jenkins job has
>>> a DISPLAY variable set which points to the server. It looks like your job
>>> is running on Windows so I don't know what issues it might be specifically.
>>> Maybe the Jenkins process doesn't have permission to access the desktop or
>>> something?
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubsc

Re: Two builds for PRs

[Mark Waite]

Unfortunately, I can't duplicate the problem.

I created a Multibranch Pipeline using
https://bitbucket.org/markewaite/jenkins-bugs/src/master/ as the Bitbucket
repository and using Bitbucket branch source cloning the repository over
https.  The repository is not a fork and has two pull requests.  When I
configure the Multibranch Pipeline job to 'Exclude branches that are also
filed as PRs', it correctly excludes the two branches that are also filed
as pull requests.  When I switch it to include only branches that are filed
as PRs, it also behaves as expected.

Sorry, I don't have other ideas to offer.  If you'd like to perform a
detailed comparison between your configuration and mine, I'd be willing to
temporarily grant you access to my Jenkins server.  Send me a private
e-mail if you'd like that access.

Mark Waite

 On Mon, Apr 1, 2019 at 2:56 PM Tom Duerr wrote:

> Hi,
>
> Ive updated core Jenkins to 2.150.3 and updated quite a few of the
> pipeline plugins.
> Here is the current list:
> https://pastebin.com/Maf6iuvQ
>
> We're still getting two PRs for each PR created from the origin and not a
> fork.
>
> I was going to try Slide's advice about filtering on branches but now that
> config option
> indicates that its been deprecated. Not sure where to configure the "Named
> Branch" plugin.
> https://imgur.com/a/smnC98S
>
>
> Other thoughts?
>
> Thanks,
> Tom
>
>
> On Friday, March 29, 2019 at 10:55:04 AM UTC-7, Tom Duerr wrote:
>>
>> I will update the pipleline related plugins this weekend and maybe
>> upgrade Jenkins (currently at 2.138 ).
>> I will report back with results.
>>
>> Thanks for the help.
>>
>> On Thu, Mar 28, 2019 at 5:29 PM Mark Waite wrote:
>>
>>>
>>>
>>> On Thu, Mar 28, 2019 at 6:22 PM Tom Duerr wrote:
>>>
>>>> Mark,
>>>> The issue only happens when the PR is NOT against a fork.  Its been
>>>> difficult to debug since most of our developers
>>>> use their own forks.
>>>>
>>>
>>> I think that is the same condition I'm using with the git client plugin
>>> multibranch configuration that I'm using.
>>>
>>>
>>>> I think I'm behind on most of the Pipeline related plugins except for
>>>> the branch-source plugin. I had attempted a big
>>>> upgrade of plugins last week that ended badly. Going to retry this
>>>> weekend.
>>>>
>>>> What is the "Jenkins multibranch folder" ? I don't think we're actively
>>>> using the multibranch plugin. Its unclear to me if we need
>>>> that plugin or not if we're already using the branch-source plugin. The
>>>> branch-source plugin seems to do everything we need
>>>> to do. I think we will eventually want to use the multibranch plugin to
>>>> provide different behaviors between a dev, qa or master branch.
>>>> Assuming I actually understand how that plugin works.
>>>>
>>>>
>>> I should have been more clear.  If you're using the GitHub branch source
>>> plugin to define the job, then you're creating a multibranch job.  The
>>> multibranch job is represented as a folder which contains one job for each
>>> branch in the repository.  The containing folder is what I called the
>>> "Jenkins multibranch folder".  No other plugin is needed.
>>>
>>> Mark Waite
>>>
>>> Tom
>>>>
>>>>
>>>>
>>>> On Thu, Mar 28, 2019 at 5:11 PM Mark Waite wrote:
>>>>
>>>>> That's quite surprising, since my PR evaluation for the git client
>>>>> plugin on my own fork is running with GitHub and is only showing the
>>>>> 'pr-merge' job.
>>>>>
>>>>> Is the second job visible when executing in the Jenkins multibranch
>>>>> folder?  If so, then I'm puzzled, because you're seeing something that I'm
>>>>> not seeing.
>>>>>
>>>>> Are you running the most recent versions of the various plugins?
>>>>>
>>>>> Mark Waite
>>>>>
>>>>> On Thu, Mar 28, 2019 at 6:06 PM Tom Duerr wrote:
>>>>>
>>>>>> Mark,
>>>>>> I already have the "Exclude branches that are also filed as PRs" set.
>>>>>> Guess that's part of my confusion.
>>>>>>
>>>>>> On Thu, Mar 28, 2019 at 4:58 PM Mark Waite wrote:
>

Re: Two builds for PRs

[Mark Waite]

I have the Basic Branch Build Strategies plugin installed in my
environment.  That seems like a worthwhile exploration to see if that
provides the desired behavior.

On Tue, Apr 2, 2019 at 12:59 PM Tom Duerr  wrote:

> A timing problem is an interesting idea but this problem seems constant.
> If its timing related, I would expect some inconsistent behaviors but you
> never can tell.
> We're using self-hosted GitHub Enterprise and sometimes it is laggy.
>
> Mark,
> Thanks, I may take you on that offer but I'm goint to try one more thing
> first. Slide has suggested that I install the "Basic Branch Build" plugin.
> Going to give that a shot.
>
> Thanks again for all your help.
> Tom
>
>
>
>
> On Tue, Apr 2, 2019 at 12:08 AM 'Björn Pedersen' via Jenkins Users <
> jenkinsci-users@googlegroups.com> wrote:
>
>> Hi,
>>
>> a wild guess: Is this a timing problem? So the push to branch gets build
>> before the pull request is filed?
>>
>>push to (new) branch
>> --->   build 1 triggered
>>  ------> file PR
>>---> build 2 triggers
>>
>>
>>
>>
>> ???
>>
>> Am Dienstag, 2. April 2019 04:21:29 UTC+2 schrieb Mark Waite:
>>>
>>> Unfortunately, I can't duplicate the problem.
>>>
>>> I created a Multibranch Pipeline using
>>> https://bitbucket.org/markewaite/jenkins-bugs/src/master/ as the
>>> Bitbucket repository and using Bitbucket branch source cloning the
>>> repository over https.  The repository is not a fork and has two pull
>>> requests.  When I configure the Multibranch Pipeline job to 'Exclude
>>> branches that are also filed as PRs', it correctly excludes the two
>>> branches that are also filed as pull requests.  When I switch it to include
>>> only branches that are filed as PRs, it also behaves as expected.
>>>
>>> Sorry, I don't have other ideas to offer.  If you'd like to perform a
>>> detailed comparison between your configuration and mine, I'd be willing to
>>> temporarily grant you access to my Jenkins server.  Send me a private
>>> e-mail if you'd like that access.
>>>
>>> Mark Waite
>>>
>>>  On Mon, Apr 1, 2019 at 2:56 PM Tom Duerr wrote:
>>>
>>>> Hi,
>>>>
>>>> Ive updated core Jenkins to 2.150.3 and updated quite a few of the
>>>> pipeline plugins.
>>>> Here is the current list:
>>>> https://pastebin.com/Maf6iuvQ
>>>>
>>>> We're still getting two PRs for each PR created from the origin and not
>>>> a fork.
>>>>
>>>> I was going to try Slide's advice about filtering on branches but now
>>>> that config option
>>>> indicates that its been deprecated. Not sure where to configure the
>>>> "Named Branch" plugin.
>>>> https://imgur.com/a/smnC98S
>>>>
>>>>
>>>> Other thoughts?
>>>>
>>>> Thanks,
>>>> Tom
>>>>
>>>>
>>>> On Friday, March 29, 2019 at 10:55:04 AM UTC-7, Tom Duerr wrote:
>>>>>
>>>>> I will update the pipleline related plugins this weekend and maybe
>>>>> upgrade Jenkins (currently at 2.138 ).
>>>>> I will report back with results.
>>>>>
>>>>> Thanks for the help.
>>>>>
>>>>> On Thu, Mar 28, 2019 at 5:29 PM Mark Waite wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Mar 28, 2019 at 6:22 PM Tom Duerr wrote:
>>>>>>
>>>>>>> Mark,
>>>>>>> The issue only happens when the PR is NOT against a fork.  Its been
>>>>>>> difficult to debug since most of our developers
>>>>>>> use their own forks.
>>>>>>>
>>>>>>
>>>>>> I think that is the same condition I'm using with the git client
>>>>>> plugin multibranch configuration that I'm using.
>>>>>>
>>>>>>
>>>>>>> I think I'm behind on most of the Pipeline related plugins except
>>>>>>> for the branch-source plugin. I had attempted a big
>>>>>>> upgrade of plugins last week that ended badly. Going to retry this
>>>>>>> weekend.
>>>>>>>
>>>>>>> What is th

Re: unable to update plugin branch-api to 2.3.0

[Mark Waite]

Branch API 2.3.0 was just released today to the Jenkins Artifactory.  The
replication process for a new release can take up to 24 hours to copy files
to correct locations.

On Thu, Apr 4, 2019 at 5:43 AM Jason Pyeron  wrote:

> When updating we get a 404 for
> http://updates.jenkins-ci.org/download/plugins/branch-api/2.3.0/branch-api.hpi
>
> http://archives.jenkins-ci.org/plugins/branch-api/ does not have a 2.3.0
> directory.
>
> -Jason
>
>
> Name
> Branch API
> This plugin provides an API for multiple branch based projects.
> Version
> 2.3.0
> Installed
> 2.2.0
>
>
> Installing Plugins/Upgrades
> Preparation
> Checking internet connectivity
> Checking update center connectivity
> Success
> Branch API
>  Failure -
> java.io.IOException: Server returned HTTP response code: 503 for URL:
> http://archives.jenkins-ci.org/plugins/branch-api/2.3.0/branch-api.hpi
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1894)
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
> at
> sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:3051)
> at
> java.net.URLConnection.getHeaderFieldLong(URLConnection.java:629)
> at
> java.net.URLConnection.getContentLengthLong(URLConnection.java:501)
> at java.net.URLConnection.getContentLength(URLConnection.java:485)
> at
> hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1158)
> Caused: java.io.IOException: Server returned HTTP response code: 503 for
> URL:
> http://archives.jenkins-ci.org/plugins/branch-api/2.3.0/branch-api.hpi
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1944)
> at
> sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1939)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1938)
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1508)
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
> at
> hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1174)
> Caused: java.io.IOException: Failed to load
> http://updates.jenkins-ci.org/download/plugins/branch-api/2.3.0/branch-api.hpi
> to /var/lib/jenkins/plugins/branch-api.jpi.tmp
> at
> hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1181)
> Caused: java.io.IOException: Failed to download from
> http://updates.jenkins-ci.org/download/plugins/branch-api/2.3.0/branch-api.hpi
> (redirected to:
> http://archives.jenkins-ci.org/plugins/branch-api/2.3.0/branch-api.hpi)
> at
> hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1215)
> at
> hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1752)
> at
> hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:2015)
> at
> hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1726)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:112)
> at java.lang.Thread.run(Thread.java:748)
>
> --
> 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/03cc01d4eadb%24aa96e460%24ffc4ad20%24%40pdinc.us
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEthLrP3EpCeUOxMGe%2BULNgsAVxy-iDbx%3DA7pNppL18_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins build numbers are in odd number 1,3,5 etc

[Mark Waite]

I installed Jenkins 2.170, created a Freestyle job, and ran the job
multiple times.  It used sequential build numbers as I expected.  Builds 1,
2, 3, 4, 5, 

I would be surprised if that were related to Jenkins 2.170.  If you can
duplicate the problem, please submit a bug report so that it can be fixed.

On Thu, Apr 4, 2019 at 6:06 AM sreeni 
wrote:

> Hi Team,
>
> I've installed the latest jenkins version 2.170, noticed that the when
> running a job, the build numbers are in odd number like 1,3,5 etc. I've
> also noticed that the builds are getting delete automatically. I ensured
> that the job is not configured to delete the old builds.
>
> I've another jenkins version 2.164 and didn't notice this behaviour. Could
> this be related to the new jenkins version 2.170 i'm using?
>
> any help would be much appreciated.
>
> thank you
>
> Regards,
> Sreenivas
>
> --
> 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/cdd44ea9-4d0a-46f6-b92c-fa4391a703f5%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/cdd44ea9-4d0a-46f6-b92c-fa4391a703f5%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHE1z6ee6D7c2BbKQP_-v2aa7jhApBYWy4bRVk-d7--tA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins build numbers are in odd number 1,3,5 etc

[Mark Waite]

tes plugin (kubernetes): 1.14.9
> Extensible Choice Parameter plugin (extensible-choice-parameter): 1.6.0
> Git Changelog (git-changelog): 2.16
>
> I'm guessing the one of the plugins is causing the issue but not sure
> which one it is. Any clue on which plugins could cause this issue would of
> be great help.
>
> Regards,
> Sreenivas
>
> --
> 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/3c430d05-1315-408d-8f85-a64d194231e4%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/3c430d05-1315-408d-8f85-a64d194231e4%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFf38LudAU1gGpHMiDMGaRWTX1XXQj1i%2BOZeGNU1nO%3Diw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to change Workspace Folder?

[Mark Waite]

Refer to
https://stackoverflow.com/questions/34854377/how-to-change-workspace-and-build-record-root-directory-on-jenkins
.
The configuration is behind an "Advanced" button on the "Configure System"
page.

On Fri, Apr 5, 2019 at 7:38 PM John Farmer  wrote:

> Jenkins CI ver 2.167 installed on Windows 10 PC, running as a Windows
> service.  The Jenkins application was installed via the Windows installer.
>
> When I ran Jenkins as a console app, it created the workspace folder
> inside the logged-in user account.  When run as a service, the workspace
> folder was created inside the "Program Files (x86)" folder (C:\Program
> Files (x86)\Jenkins\workspace).
>
> How can I change the location of the workspace folder outside of the
> program files path?
>
> --
> 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/32803ae1-975a-4d6b-82c3-a81cedd3af97%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/32803ae1-975a-4d6b-82c3-a81cedd3af97%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtGu-p9A9qmUA9EAkXx3-tS76u6VX3QTb_kNgjVfcMjgRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Windows Slave GIT_SSH Invalid format

[Mark Waite]

 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)
>   at 
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113)
>   at 
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85)
>   at 
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75)
>   at 
> org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
>   at hudson.security.ACL.impersonate(ACL.java:290)
>   at 
> org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
>
>
>
>
>
>
>
>
>
> --
> 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/8c3b499c-73fa-42f6-bd13-5fdac28ef320%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/8c3b499c-73fa-42f6-bd13-5fdac28ef320%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEkiszK3qMir__%2BUC_Z8sZu_tAX0aO4eewsKXVP8LdjDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Windows Slave GIT_SSH Invalid format

[Mark Waite]

I've seen problems in the past where I needed to generate the private key /
public key pair on the machine that would be using the key.  When you
created the private key, did you run ssh-keygen on the Windows computer
that is using the key?  If not, you might try that.

On Wed, Apr 10, 2019 at 11:23 AM Venkatapathi Jaligama 
wrote:

> Hello Mark,
> Thank you for you prompt response, I have already tested this scenario
> also removed all the jeys from windows slave and only use the jenkins
> credentials still does not work, I generated new keys and added the private
> key in the jenkins credentials and public key in Gitlab still same issue.
> Could you think of anything else.
>
> Thanks,
> Venkat
>
> On Wed, Apr 10, 2019 at 11:43 AM Mark Waite 
> wrote:
>
>> Compare the contents of the private key definition in the Jenkins
>> credentials UI with the private key that is being used on the Windows
>> agent.  If the key is incorrectly defined in the Jenkins credentials, that
>> might cause the problem you're seeing.
>>
>> Move (or hide) all other private keys on the Windows agent to be sure
>> that your successful interactive test was not using a different private key
>> than the private key used in the Jenkins credential.
>>
>> On Wed, Apr 10, 2019 at 3:47 AM  wrote:
>>
>>> Hello Users,
>>>
>>> I have Jenkins with master slave configuration, I have linux slaves and
>>> windows slaves
>>> I am unable to use the Gitlab  SSH credentials on Windows Slave
>>> Fails on scm checkout, The scm checkout works fine for the linux slaves
>>> To test the id_rsa key, I put the id_rsa in .ssh of home directory  and
>>> do git clone, it works fine, but somehow from git credentials it seem to
>>> have a problem
>>> Is there a workaround for this issue any help is very much appreciated
>>>
>>> using credential 2090ffbd-ddc3-45a9-adfb-e9c0e5ca4c75
>>> Wiping out workspace first.
>>> Cloning the remote Git repository
>>> Cloning repository ssh://g...@gitlab-.com/xx.git
>>>  > git init 
>>> E:\workspace\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ
>>>  # timeout=10
>>> Fetching upstream changes from ssh://g...@gitlab-.com/xx.git
>>>  > git --version # timeout=10
>>> using GIT_SSH to set credentials Jenkins private ssh key
>>>  > git fetch --tags --progress ssh://g...@gitlab-.com/xx.git 
>>> +refs/heads/*:refs/remotes/origin/* # timeout=7
>>> ERROR: Error cloning remote repo 'origin'
>>> hudson.plugins.git.GitException: Command "git fetch --tags --progress 
>>> ssh://g...@gitlab-.com/xx.git +refs/heads/*:refs/remotes/origin/*" 
>>> returned status code 128:
>>> stdout:
>>> stderr: Load key 
>>> "E:\\workspace\\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ@tmp\\ssh8872120221702825356.key":
>>>  invalid format
>>> Permission denied, please try again.
>>> Permission denied, please try again@gitlab-.com/xx.git: Permission 
>>> denied (publickey,gssapi-keyex,gssapi-with-mic,password).
>>> fatal: Could not read from remote repository.
>>>
>>> Please make sure you have the correct access rights
>>> and the repository exists.
>>>
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2002)
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1721)
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72)
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405)
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:614)
>>> at 
>>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
>>> at 
>>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
>>> at hudson.remoting.UserRequest.perform(UserRequest.java:212)
>>> at hudson.remoting.UserRequest.perform(UserRequest.java:54)
>>> at hudson.remoting.Request$2.run(Request.java:369)
>>> at 
>>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>>> at java.util.concurrent.FutureTask.run(Unknown Source)
>>> at java.util.concurrent.ThreadPoolExecutor.ru

Re: Jenkins Windows Slave GIT_SSH Invalid format

[Mark Waite]

I'd create the keys on Windows using the ssh-keygen command on Windows.
OpenSSH on Windows will be consuming the keys.

On Wed, Apr 10, 2019 at 11:43 AM Venkatapathi Jaligama 
wrote:

> Hello Mark,
>
> First time i created key on linux, second-time I created on windows slave
> from putty gen and convert to openssh format and then use the keys, even
> these keys work for linux slaves but not for windows slave, gives invalid
> format
>
> On Wed, Apr 10, 2019 at 1:38 PM Mark Waite 
> wrote:
>
>> I've seen problems in the past where I needed to generate the private key
>> / public key pair on the machine that would be using the key.  When you
>> created the private key, did you run ssh-keygen on the Windows computer
>> that is using the key?  If not, you might try that.
>>
>> On Wed, Apr 10, 2019 at 11:23 AM Venkatapathi Jaligama <
>> jvenkat...@gmail.com> wrote:
>>
>>> Hello Mark,
>>> Thank you for you prompt response, I have already tested this scenario
>>> also removed all the jeys from windows slave and only use the jenkins
>>> credentials still does not work, I generated new keys and added the private
>>> key in the jenkins credentials and public key in Gitlab still same issue.
>>> Could you think of anything else.
>>>
>>> Thanks,
>>> Venkat
>>>
>>> On Wed, Apr 10, 2019 at 11:43 AM Mark Waite 
>>> wrote:
>>>
>>>> Compare the contents of the private key definition in the Jenkins
>>>> credentials UI with the private key that is being used on the Windows
>>>> agent.  If the key is incorrectly defined in the Jenkins credentials, that
>>>> might cause the problem you're seeing.
>>>>
>>>> Move (or hide) all other private keys on the Windows agent to be sure
>>>> that your successful interactive test was not using a different private key
>>>> than the private key used in the Jenkins credential.
>>>>
>>>> On Wed, Apr 10, 2019 at 3:47 AM  wrote:
>>>>
>>>>> Hello Users,
>>>>>
>>>>> I have Jenkins with master slave configuration, I have linux slaves
>>>>> and windows slaves
>>>>> I am unable to use the Gitlab  SSH credentials on Windows Slave
>>>>> Fails on scm checkout, The scm checkout works fine for the linux
>>>>> slaves
>>>>> To test the id_rsa key, I put the id_rsa in .ssh of home directory
>>>>> and do git clone, it works fine, but somehow from git credentials it seem
>>>>> to have a problem
>>>>> Is there a workaround for this issue any help is very much appreciated
>>>>>
>>>>> using credential 2090ffbd-ddc3-45a9-adfb-e9c0e5ca4c75
>>>>> Wiping out workspace first.
>>>>> Cloning the remote Git repository
>>>>> Cloning repository ssh://g...@gitlab-.com/xx.git
>>>>>  > git init 
>>>>> E:\workspace\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ
>>>>>  # timeout=10
>>>>> Fetching upstream changes from ssh://g...@gitlab-.com/xx.git
>>>>>  > git --version # timeout=10
>>>>> using GIT_SSH to set credentials Jenkins private ssh key
>>>>>  > git fetch --tags --progress ssh://g...@gitlab-.com/xx.git 
>>>>> +refs/heads/*:refs/remotes/origin/* # timeout=7
>>>>> ERROR: Error cloning remote repo 'origin'
>>>>> hudson.plugins.git.GitException: Command "git fetch --tags --progress 
>>>>> ssh://g...@gitlab-.com/xx.git +refs/heads/*:refs/remotes/origin/*" 
>>>>> returned status code 128:
>>>>> stdout:
>>>>> stderr: Load key 
>>>>> "E:\\workspace\\Main_Build_master-HAJ7MPMVYIUEWROZ6RHLXJYVT3JUCE7ZDT7PHAOWUKJQYMDSW5KQ@tmp\\ssh8872120221702825356.key":
>>>>>  invalid format
>>>>> Permission denied, please try again.
>>>>> Permission denied, please try again@gitlab-.com/xx.git: 
>>>>> Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
>>>>> fatal: Could not read from remote repository.
>>>>>
>>>>> Please make sure you have the correct access rights
>>>>> and the repository exists.
>>>>>
>>>>>   at 
>>>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2002)
>>>>>   at 
>>>>> org.jenkinsci.plugins.gitcl

Re: Install JDK Oracle 8 update 211

[Mark Waite]

I see Oracle Java SE Development Kit 8u211 at
https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
 .

If that were not available, you could also consider downloading the Amazon
Corretto 8 from
https://docs.aws.amazon.com/corretto/latest/corretto-8-ug/downloads-list.html

On Wed, Apr 17, 2019 at 5:57 AM  wrote:

> Hi,
>
> How do i have to install this JDK while it is not in listed from
> java.sun.com
>
> With kind regards, Wil
>
> --
> 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/9b833d57-b1b4-4448-a030-3d8b18284d84%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/9b833d57-b1b4-4448-a030-3d8b18284d84%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEGyBhVO_TBcGLruVHEYUsr3eJK0fB5bb-qBvZRaT8kRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Install JDK Oracle 8 update 211

[Mark Waite]

Review the new terms of the license agreement for Oracle JDK 8.  If they
are acceptable, then you can download the Oracle JDK binaries, place them
on a local location where your agents can find them, and add a JDK
installer to Jenkins for that location.

The new Oracle JDK 8 license terms are more restrictive than the previous
terms.

On Wed, Apr 17, 2019 at 8:31 AM  wrote:

> Hi,
>
> Thank you for your quick reply Mark, but that's not the answer to my
> question.I don't think my question is clear.
>
> In Jenkins > Manage > Global Tool Configuration > JDK installlations you
> can install a JDK with the installer from java.sun.com
> Normaly it is possible to select a JDK from a drop-down list, but JDK 8
> update 211 is not in that list available. What is the procedure to install
> this JDK version.
>
> With kind regards, Wil
>
>
> Op woensdag 17 april 2019 15:21:26 UTC+2 schreef Mark Waite:
>>
>> I see Oracle Java SE Development Kit 8u211 at
>> https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
>>  .
>>
>> If that were not available, you could also consider downloading the
>> Amazon Corretto 8 from
>> https://docs.aws.amazon.com/corretto/latest/corretto-8-ug/downloads-list.html
>>
>> On Wed, Apr 17, 2019 at 5:57 AM  wrote:
>>
>>> Hi,
>>>
>>> How do i have to install this JDK while it is not in listed from
>>> java.sun.com
>>>
>>> With kind regards, Wil
>>>
>>> --
>>> 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 jenkins...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/9b833d57-b1b4-4448-a030-3d8b18284d84%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/9b833d57-b1b4-4448-a030-3d8b18284d84%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> 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/a48a2df9-9db1-413c-ade9-390ba0dda8c9%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/a48a2df9-9db1-413c-ade9-390ba0dda8c9%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtGuGmSzYWZG%3DqesiwF-79mL-%2ByghqGOrHh5cXmW9ReB8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cloud Master / On-Prem Slave

[Mark Waite]

If your on premise agents (slaves) can connect to the JNLP port of the
cloud master (usually port 5), then they could be added as agents
(slaves) of your cloud master using the "Java Web Start" method.  That
requires the agent initiates the connection to the master JNLP port and the
master needs to be willing to accept the connection on that port.

If your cloud master can initiate an ssh connection to your on-premise
agents, then you could add the on-premise agents using the ssh-slaves
plugin.  That requires the master initiates the connection to the agent ssh
port and the agents need to be willing to accept the connection on the ssh
port.

Mark Waite

On Thu, Apr 18, 2019 at 7:39 AM Steve B  wrote:

> I am fairly new to Jenkins.  We have used it on-prem for some builds.
> Development has started using Jenkins in the cloud for new features and I
> was wondering if I can have the Jenkins Master that is in the Cloud send
> jobs to my On-Prem slaves?
>
> Looks like there are some services that allow some sort on "Hybrid"
> systems but I don't think we can go for that at this time.
>
> 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/1e2270ea-b3cb-43d1-98c4-9d4f2c9f6948%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/1e2270ea-b3cb-43d1-98c4-9d4f2c9f6948%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFd2S%2B_T7QtwwL0i0bjKy%3DoQd3PLrW44SewR75%3Dyqdb%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Install JDK Oracle 8 update 211

[Mark Waite]

That location should be an HTTP server somewhere in your local network.  If
you place the zip file or the tar.gz file in the JENKINS_HOME/userContent
directory, then you could make the download location be
https://yourjenkins/userContent/filemame.zip .

Alternately, if you have a local HTTP server that is used to deliver other
static content, you could place that file on that HTTP server.

Mark Waite

On Wed, Apr 17, 2019 at 10:29 AM  wrote:

> Hi,
>
> Thank you Mark.
> I use the *Extract *.zip/*.tar.gz installer.*
> *I downloaded the jdk-8u212-windows-x64.exe file, i converted to a .zip
> archive and put it on a specific location, but in Jenkins i must fill in he
> download location for the binary archive. I'm sorry, but i don't know the
> exact url.*
> *Please can you help me?*
>
>
> *With kind regards*
>
> Op woensdag 17 april 2019 16:41:05 UTC+2 schreef Mark Waite:
>>
>> Review the new terms of the license agreement for Oracle JDK 8.  If they
>> are acceptable, then you can download the Oracle JDK binaries, place them
>> on a local location where your agents can find them, and add a JDK
>> installer to Jenkins for that location.
>>
>> The new Oracle JDK 8 license terms are more restrictive than the previous
>> terms.
>>
>> On Wed, Apr 17, 2019 at 8:31 AM  wrote:
>>
>>> Hi,
>>>
>>> Thank you for your quick reply Mark, but that's not the answer to my
>>> question.I don't think my question is clear.
>>>
>>> In Jenkins > Manage > Global Tool Configuration > JDK installlations you
>>> can install a JDK with the installer from java.sun.com
>>> Normaly it is possible to select a JDK from a drop-down list, but JDK 8
>>> update 211 is not in that list available. What is the procedure to install
>>> this JDK version.
>>>
>>> With kind regards, Wil
>>>
>>>
>>> Op woensdag 17 april 2019 15:21:26 UTC+2 schreef Mark Waite:
>>>>
>>>> I see Oracle Java SE Development Kit 8u211 at
>>>> https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
>>>>  .
>>>>
>>>> If that were not available, you could also consider downloading the
>>>> Amazon Corretto 8 from
>>>> https://docs.aws.amazon.com/corretto/latest/corretto-8-ug/downloads-list.html
>>>>
>>>> On Wed, Apr 17, 2019 at 5:57 AM  wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> How do i have to install this JDK while it is not in listed from
>>>>> java.sun.com
>>>>>
>>>>> With kind regards, Wil
>>>>>
>>>>> --
>>>>> 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 jenkins...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/jenkinsci-users/9b833d57-b1b4-4448-a030-3d8b18284d84%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/9b833d57-b1b4-4448-a030-3d8b18284d84%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks!
>>>> 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 jenkins...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/a48a2df9-9db1-413c-ade9-390ba0dda8c9%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/a48a2df9-9db1-413c-ade9-390ba0dda8c9%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> 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/dc223758-5a0a-49b6-9be3-84c384a3f958%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/dc223758-5a0a-49b6-9be3-84c384a3f958%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFn7mNwi_QjJFD%3DzXHp9c7Eay4jvuPoaJ47EucQ9GkgVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins hints for large git repos

[Mark Waite]

I presented a 10-15 minute section called "Git in the Large - Hints for
Large Git Repos" at https://youtu.be/jBGFjFc6Jf8?t=6432 .  A slightly older
version on a similar theme is available at
https://youtu.be/TsWkZLLU-s4?t=139 .

Slides from the second talk are available at
https://jenkins.io/files/2016/jenkins-world/large-git-repos.pdf .  Slides
from the first talk are available at
https://www.slideshare.net/markewaite/git-inthelarge

Short answer - use a reference repository to dramatically reduce repository
disc space for multiple repositories.  Use a narrow refspec to reduce data
transfer and disc space in repositories with many divergent branches.  Use
a shallow clone to reduce data transfer and disc use.

Mark Waite

On Thu, Apr 18, 2019 at 8:37 AM b o b i  wrote:

>
> Jenkins scripted pipeline
> Git repo 2.6G
>
> Each job wants to git clone the latest commit
>
> #Jobs x GitRepo = many GB disk space.
>
> Do you have any hints of how to reduce the disk space usage, i.e. any
> hints how to deal with large git repors by many jobs ?
>
> --
> 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/1043d9ff-586e-4fd0-8791-0d7dd2e401aa%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/1043d9ff-586e-4fd0-8791-0d7dd2e401aa%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHKiYF2UiVfVA3BPD-DyNvGfjrOJFnv6zTNyrNaCo8e5A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins git plugin using only Java 7.1

[Mark Waite]

Git plugin 3.9.x does not mandate Java 8 of itself.  The git plugin 3.9.x
compile environment checks that the generated byte code is only Java 7.
However, as you have discovered, that does not check that all its
dependencies only require Java 7.

I think you're stuck performing a search through the git plugin history to
locate a version that does not include any dependencies on a Java 8
component.

Mark Waite

On Tue, Apr 23, 2019 at 2:18 AM Rich Stephens  wrote:

>
> Yes I’m aware that Jenkins moved on to Java 8 long ago,
> But because of the environment I’m using, I’m restricted to going no
> higher than Java 7.
>
> I was afraid the answer would be what you are saying, but thanks for the
> 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/e960820c-4221-4b2c-a6ea-08725a782807%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtE4EHBSF7n2omwDfSy0dh5WO%3DfPD8M5bEf%3DV2EVPOWqbQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins git plugin using only Java 7.1

[Mark Waite]

The Jenkins platform special interest group in gitter might also have 
people with related interests, in case you want to try posting your 
question there.

https://gitter.im/jenkinsci/platform-sig

I've not seen any discussions on this topic in the platform-sig, but there 
have been discussions about mainframe support and about multi-platform 
support for Docker images.

Mark Waite


On Tuesday, April 23, 2019 at 6:22:18 AM UTC-5, Mark Waite wrote:
>
> Git plugin 3.9.x does not mandate Java 8 of itself.  The git plugin 3.9.x 
> compile environment checks that the generated byte code is only Java 7.  
> However, as you have discovered, that does not check that all its 
> dependencies only require Java 7.
>
> I think you're stuck performing a search through the git plugin history to 
> locate a version that does not include any dependencies on a Java 8 
> component.
>
> Mark Waite
>
> On Tue, Apr 23, 2019 at 2:18 AM Rich Stephens  wrote:
>
>>
>> Yes I’m aware that Jenkins moved on to Java 8 long ago,
>> But because of the environment I’m using, I’m restricted to going no 
>> higher than Java 7.
>>
>> I was afraid the answer would be what you are saying, but thanks for the 
>> information.
>>
>> -- 
>>
>
> -- 
> Thanks!
> 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/47978977-3dd0-478a-acd7-32c419688c79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker-Hub jenkins or jenkinsci?

[Mark Waite]

On Wed, Apr 24, 2019 at 7:19 AM 'Sven Hüßner' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> There are two organisations on Docker-Hub that have Jenkins images:
> https://hub.docker.com/u/jenkins
> and
> https://hub.docker.com/u/jenkinsci
>
>
https://hub.docker.com/r/jenkinsci/jenkins reports that the repository is
deprecated in favor of the https://hub.docker.com/r/jenkins/jenkins/ image.

Use the "jenkins" image from DockerHub, not the "jenkinsci" image.  The
Jenkins project controls the "jenkins" image.  The DockerHub team controls
the "jenkinsci" image.


> They both seem to have the "blueocean" variant for example. The
> jenkins/blueocean <https://hub.docker.com/r/jenkins/blueocean> seems to
> be pretty unused though, as compared to the jenkinsci/blueocean
> <https://hub.docker.com/r/jenkinsci/blueocean>.
>
> So which image would I pull from which organization? And how are they
> different? It's a bit confusing.
>

The "jenkinsci/blueocean" image includes many more components than the
"jenkinsci/jenkins" image.  Docker in docker is one of the things that the
blueocean image includes.  That Docker in docker support is used to make
the tutorials on jenkins.io deeper and more valuable to those using the
image to learn more about Jenkins.

I've understood that there are security risks associated with running
docker in docker.  I have preferred to use the jenkinsci/jenkins image as
the basis for my work, then I add the plugins I want (including Blue Ocean).

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/929bd5a2-4e68-49b2-979c-9786103ab1d6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/929bd5a2-4e68-49b2-979c-9786103ab1d6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtESfNLjKqSB8DgVeG8Dnk89yFfPW5t9ie7Od9em_Ezf%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.164 Prompting Terminal for Passphrase

[Mark Waite]

On Wed, Apr 24, 2019 at 11:09 AM Randall Becker wrote:

> This is a new situation that I have encountered after a clean install of
> 2.164. Attempting to use an SSH keypair (with passphrase) to talk to
> BitBucket.org, in a Multibranch Pipeline job. The key is properly
> configured as an Private Key (entered manually) with a Passphrase.
>
> When I hit Scan Multibranch Pipeline Now, Jenkins immediately prompts the
> JVM's stderr for the passphrase. As an example:
>
> Enter passphrase for key '/tmp/ssh6766884284790436436.key':
>
> I also get an error in the Multibranch scan log:
>
>  > git ls-remote g...@bitbucket.org:group/repo.git # edited, of course
> ERROR: [Wed Apr 24 16:58:41 UTC 2019] Could not update folder level actions 
> from source 73a4292e-
> hudson.plugins.git.GitException: Command "git ls-remote 
> g...@bitbucket.org:group/repo.git" returned status code 128:
> stdout:
> stderr: Permission denied (publickey).
> fatal: Could not read from remote repository.
>
>
> This is bizarre. I'm running Ubuntu 16.04 using the default JRE. This did
> not happen on earlier versions of Jenkins that were running in Docker
> images - I had to remove Docker for VPN reasons.
>
> I'm basically off the air at this point. Did I just miss a plugin or do
> something silly?
>
>
Command line git uses ssh for communications with git servers through the
secure shell protocol.  The ssh command is designed to prompt the user for
the passphrase.  The ssh command prompts for a passphrase in cases that are
sometimes surprising (at least for the git plugin).  You probably have one
of those cases.

I would guess that your Jenkins server process (the Java process running
the master) is attached to a controlling terminal or it has environment
variables set which make the ssh command line process believe that it is
attached to a controlling terminal.  That causes the ssh command line to
prompt for the passphrase on the private key.

Refer to
https://github.com/jenkinsci/git-client-plugin/commit/882ecdfb53d627a130720685681ce2553193
for
the commit message that describes the change that was made in the git
client plugin to handle that case, and the property you can set to enable
that change.

Alternatives you can choose:

   1. Run Jenkins without a controlling terminal (for example, if running
   in Docker, be sure that you "detach")
   2. Use private keys without passphrases
   3. Set the Java
   property org.jenkinsci.plugins.gitclient.CliGitAPIImpl.useSETSID=true on
   the command line that starts the master

I suspect that the critical difference between your prior condition and the
current condition is that the Jenkins process is now attached to a
controlling terminal.

Mark Waite



> TIA,
> Randall
>
> --
> 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/cf306a8d-14c2-4ebc-9173-3ddeab0a1020%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/cf306a8d-14c2-4ebc-9173-3ddeab0a1020%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEfqfYqPKqdL79i2kNRYCvPaB8SJnswcOicHagdV5KbdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.164 Prompting Terminal for Passphrase

[Mark Waite]

On Wed, Apr 24, 2019 at 11:32 AM Mark Waite 
wrote:

>
>
> On Wed, Apr 24, 2019 at 11:09 AM Randall Becker wrote:
>
>> This is a new situation that I have encountered after a clean install of
>> 2.164. Attempting to use an SSH keypair (with passphrase) to talk to
>> BitBucket.org, in a Multibranch Pipeline job. The key is properly
>> configured as an Private Key (entered manually) with a Passphrase.
>>
>> When I hit Scan Multibranch Pipeline Now, Jenkins immediately prompts the
>> JVM's stderr for the passphrase. As an example:
>>
>> Enter passphrase for key '/tmp/ssh6766884284790436436.key':
>>
>> I also get an error in the Multibranch scan log:
>>
>>  > git ls-remote g...@bitbucket.org:group/repo.git # edited, of course
>> ERROR: [Wed Apr 24 16:58:41 UTC 2019] Could not update folder level actions 
>> from source 73a4292e-
>> hudson.plugins.git.GitException: Command "git ls-remote 
>> g...@bitbucket.org:group/repo.git" returned status code 128:
>> stdout:
>> stderr: Permission denied (publickey).
>> fatal: Could not read from remote repository.
>>
>>
>> This is bizarre. I'm running Ubuntu 16.04 using the default JRE. This did
>> not happen on earlier versions of Jenkins that were running in Docker
>> images - I had to remove Docker for VPN reasons.
>>
>> I'm basically off the air at this point. Did I just miss a plugin or do
>> something silly?
>>
>>
> Command line git uses ssh for communications with git servers through the
> secure shell protocol.  The ssh command is designed to prompt the user for
> the passphrase.  The ssh command prompts for a passphrase in cases that are
> sometimes surprising (at least for the git plugin).  You probably have one
> of those cases.
>
> I would guess that your Jenkins server process (the Java process running
> the master) is attached to a controlling terminal or it has environment
> variables set which make the ssh command line process believe that it is
> attached to a controlling terminal.  That causes the ssh command line to
> prompt for the passphrase on the private key.
>
> Refer to
> https://github.com/jenkinsci/git-client-plugin/commit/882ecdfb53d627a130720685681ce2553193
>  for
> the commit message that describes the change that was made in the git
> client plugin to handle that case, and the property you can set to enable
> that change.
>
> Alternatives you can choose:
>
>1. Run Jenkins without a controlling terminal (for example, if running
>in Docker, be sure that you "detach")
>2. Use private keys without passphrases
>3. Set the Java
>property org.jenkinsci.plugins.gitclient.CliGitAPIImpl.useSETSID=true on
>the command line that starts the master
>
>
Alternative 4 may also be viable - enable JGit as a git implementation and
use JGit rather than command line git.  The command line git implementation
is the reference implementation, but there are many use cases where the
JGit implementation is good enough to do the job as well.

Mark Waite

I suspect that the critical difference between your prior condition and the
> current condition is that the Jenkins process is now attached to a
> controlling terminal.
>
> Mark Waite
>
>
>
>> TIA,
>> Randall
>>
>> --
>> 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/cf306a8d-14c2-4ebc-9173-3ddeab0a1020%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/cf306a8d-14c2-4ebc-9173-3ddeab0a1020%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Thanks!
> Mark Waite
>


-- 
Thanks!
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/CAO49JtEXMT1p61J7bjVXYJFBXtAc1cx2sacAjEWAjvRDHYp-rw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.164 Prompting Terminal for Passphrase

[Mark Waite]

On Wed, Apr 24, 2019 at 12:05 PM Randall Becker 
wrote:

> Thanks, however, I'm not sure this is it. My startup script is:
>
> unset TERM # Not really useful
> nohup java \
> -Dorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.useSETSID=true \
> -jar jenkins.war \
> < /dev/null 2>&1 \
> > jenkins.log &
>
> which should not be attached to a terminal, but is. The define seems to
> have no effect. There are no SSH variables in the environment. And, most
> importantly, I cannot use a passphrase-less keypair to talk to
> bitbucket.org without being fired. Did I miss something?
>

-Dorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.useSETSID=true is what I
use.  Are you running git client plugin 2.4.2 or later?

You could also try prefixing the java process with setsid instead of nohup,
in case that behaves better with command line ssh.


>
> On Wednesday, April 24, 2019 at 1:08:48 PM UTC-4, Randall Becker wrote:
>>
>> This is a new situation that I have encountered after a clean install of
>> 2.164. Attempting to use an SSH keypair (with passphrase) to talk to
>> BitBucket.org, in a Multibranch Pipeline job. The key is properly
>> configured as an Private Key (entered manually) with a Passphrase.
>>
>> When I hit Scan Multibranch Pipeline Now, Jenkins immediately prompts the
>> JVM's stderr for the passphrase. As an example:
>>
>> Enter passphrase for key '/tmp/ssh6766884284790436436.key':
>>
>> I also get an error in the Multibranch scan log:
>>
>>  > git ls-remote g...@bitbucket.org:group/repo.git # edited, of course
>> ERROR: [Wed Apr 24 16:58:41 UTC 2019] Could not update folder level actions 
>> from source 73a4292e-
>> hudson.plugins.git.GitException: Command "git ls-remote 
>> g...@bitbucket.org:group/repo.git" returned status code 128:
>> stdout:
>> stderr: Permission denied (publickey).
>> fatal: Could not read from remote repository.
>>
>>
>> This is bizarre. I'm running Ubuntu 16.04 using the default JRE. This did
>> not happen on earlier versions of Jenkins that were running in Docker
>> images - I had to remove Docker for VPN reasons.
>>
>> I'm basically off the air at this point. Did I just miss a plugin or do
>> something silly?
>>
>> TIA,
>> Randall
>>
> --
> 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/8c70123f-5388-48cc-a6b8-dcca6d36fb00%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/8c70123f-5388-48cc-a6b8-dcca6d36fb00%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFFo-fgPP4hv2xr-4uN9%3D89y2L7sHRt5Oro6yx3DfDaMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.164 Prompting Terminal for Passphrase

[Mark Waite]

On Wed, Apr 24, 2019 at 12:10 PM Randall Becker wrote:

> I'll bite. How can I use JGit instead of git in Jenkins? I thought it was
> hard-burnt into the Git Plugin.
>
>
In the "Global Tools Configuration" page of "Manage Jenkins", use the "Git"
button and the "Add" button under it to add "jgit" as an implementation.
Once you've done that, then jobs will have an additional option to select
which git implementation they will use.


> On Wednesday, April 24, 2019 at 1:08:48 PM UTC-4, Randall Becker wrote:
>>
>> This is a new situation that I have encountered after a clean install of
>> 2.164. Attempting to use an SSH keypair (with passphrase) to talk to
>> BitBucket.org, in a Multibranch Pipeline job. The key is properly
>> configured as an Private Key (entered manually) with a Passphrase.
>>
>> When I hit Scan Multibranch Pipeline Now, Jenkins immediately prompts the
>> JVM's stderr for the passphrase. As an example:
>>
>> Enter passphrase for key '/tmp/ssh6766884284790436436.key':
>>
>> I also get an error in the Multibranch scan log:
>>
>>  > git ls-remote g...@bitbucket.org:group/repo.git # edited, of course
>> ERROR: [Wed Apr 24 16:58:41 UTC 2019] Could not update folder level actions 
>> from source 73a4292e-
>> hudson.plugins.git.GitException: Command "git ls-remote 
>> g...@bitbucket.org:group/repo.git" returned status code 128:
>> stdout:
>> stderr: Permission denied (publickey).
>> fatal: Could not read from remote repository.
>>
>>
>> This is bizarre. I'm running Ubuntu 16.04 using the default JRE. This did
>> not happen on earlier versions of Jenkins that were running in Docker
>> images - I had to remove Docker for VPN reasons.
>>
>> I'm basically off the air at this point. Did I just miss a plugin or do
>> something silly?
>>
>> TIA,
>> Randall
>>
> --
> 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/30f56e57-d3de-4e43-96dc-d07aa4ebdcda%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/30f56e57-d3de-4e43-96dc-d07aa4ebdcda%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFxKTNA-8jK-u2%3Dj6WLOVDnGsQVnAFVDBvBJnSsHtoV9A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.164 Prompting Terminal for Passphrase

[Mark Waite]

On Wed, Apr 24, 2019 at 12:33 PM Randall Becker wrote:

> The Multibranch Pipeline Plugin using JGit ends up incompatible.
>
>  > /usr/local/bin/jgit --version # timeout=10
>  > /usr/local/bin/jgit ls-remote --symref 
> g...@bitbucket.org:nonstop-git/nsgit.git # timeout=10
>
> ERROR: [Wed Apr 24 18:23:01 UTC 2019] Could not update folder level actions 
> from source 0819144a...
> hudson.plugins.git.GitException: Command "/usr/local/bin/jgit ls-remote 
> --symref g...@bitbucket.org:group/repo.git" returned status code 1:
> stdout:
> stderr: fatal: "--symref" is not a valid option
>
> That indicates you created a new name for the command line git
implementation and named it 'jgit'.  That's not what you want to do.

You want to add 'jgit' as one of the available implementations.

The configuration screen should look like this:

[image: image.png]


> Looks like JGit (5.3.0 anyway) is no longer an option for polling. I'm on
> Git Plugin 3.9.3.
>
> setsid made no difference.
>
> On Wednesday, April 24, 2019 at 2:24:00 PM UTC-4, Mark Waite wrote:
>>
>>
>>
>> On Wed, Apr 24, 2019 at 12:10 PM Randall Becker wrote:
>>
>>> I'll bite. How can I use JGit instead of git in Jenkins? I thought it
>>> was hard-burnt into the Git Plugin.
>>>
>>>
>> In the "Global Tools Configuration" page of "Manage Jenkins", use the
>> "Git" button and the "Add" button under it to add "jgit" as an
>> implementation.  Once you've done that, then jobs will have an additional
>> option to select which git implementation they will use.
>>
>>
>>> On Wednesday, April 24, 2019 at 1:08:48 PM UTC-4, Randall Becker wrote:
>>>>
>>>> This is a new situation that I have encountered after a clean install
>>>> of 2.164. Attempting to use an SSH keypair (with passphrase) to talk to
>>>> BitBucket.org, in a Multibranch Pipeline job. The key is properly
>>>> configured as an Private Key (entered manually) with a Passphrase.
>>>>
>>>> When I hit Scan Multibranch Pipeline Now, Jenkins immediately prompts
>>>> the JVM's stderr for the passphrase. As an example:
>>>>
>>>> Enter passphrase for key '/tmp/ssh6766884284790436436.key':
>>>>
>>>> I also get an error in the Multibranch scan log:
>>>>
>>>>  > git ls-remote g...@bitbucket.org:group/repo.git # edited, of course
>>>> ERROR: [Wed Apr 24 16:58:41 UTC 2019] Could not update folder level 
>>>> actions from source 73a4292e-
>>>> hudson.plugins.git.GitException: Command "git ls-remote 
>>>> g...@bitbucket.org:group/repo.git" returned status code 128:
>>>> stdout:
>>>> stderr: Permission denied (publickey).
>>>> fatal: Could not read from remote repository.
>>>>
>>>>
>>>> This is bizarre. I'm running Ubuntu 16.04 using the default JRE. This
>>>> did not happen on earlier versions of Jenkins that were running in Docker
>>>> images - I had to remove Docker for VPN reasons.
>>>>
>>>> I'm basically off the air at this point. Did I just miss a plugin or do
>>>> something silly?
>>>>
>>>> TIA,
>>>> Randall
>>>>
>>> --
>>> 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 jenkins...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/30f56e57-d3de-4e43-96dc-d07aa4ebdcda%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/30f56e57-d3de-4e43-96dc-d07aa4ebdcda%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> 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/f475e8c0-ab7a-421b-9bcd-95a85ecb8c67%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/f475e8c0-ab7a-421b-9bcd-95a85ecb8c67%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEKDg2FAv_8iJAYhDZZ7PdPFgBtbPUwUEmM2dothr6gpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.164 Prompting Terminal for Passphrase

[Mark Waite]

On Wed, Apr 24, 2019 at 12:35 PM Randall Becker 
wrote:

> I should qualify... the passphrase prompt disappeared when setsid is used,
> but that still does not allow a passphrase-less keypair.
>
>
That may indicate that you have another problem.  If the passphrase prompt
disappeared, then ssh should have either completed the ssh authentication
or reported an error message.


> On Wednesday, April 24, 2019 at 2:33:07 PM UTC-4, Randall Becker wrote:
>>
>> The Multibranch Pipeline Plugin using JGit ends up incompatible.
>>
>>  > /usr/local/bin/jgit --version # timeout=10
>>  > /usr/local/bin/jgit ls-remote --symref 
>> g...@bitbucket.org:nonstop-git/nsgit.git # timeout=10
>>
>> ERROR: [Wed Apr 24 18:23:01 UTC 2019] Could not update folder level actions 
>> from source 0819144a...
>> hudson.plugins.git.GitException: Command "/usr/local/bin/jgit ls-remote 
>> --symref g...@bitbucket.org:group/repo.git" returned status code 1:
>> stdout:
>> stderr: fatal: "--symref" is not a valid option
>>
>> Looks like JGit (5.3.0 anyway) is no longer an option for polling. I'm on
>> Git Plugin 3.9.3.
>>
>> setsid made no difference.
>>
>> On Wednesday, April 24, 2019 at 2:24:00 PM UTC-4, Mark Waite wrote:
>>>
>>>
>>>
>>> On Wed, Apr 24, 2019 at 12:10 PM Randall Becker wrote:
>>>
>>>> I'll bite. How can I use JGit instead of git in Jenkins? I thought it
>>>> was hard-burnt into the Git Plugin.
>>>>
>>>>
>>> In the "Global Tools Configuration" page of "Manage Jenkins", use the
>>> "Git" button and the "Add" button under it to add "jgit" as an
>>> implementation.  Once you've done that, then jobs will have an additional
>>> option to select which git implementation they will use.
>>>
>>>
>>>> On Wednesday, April 24, 2019 at 1:08:48 PM UTC-4, Randall Becker wrote:
>>>>>
>>>>> This is a new situation that I have encountered after a clean install
>>>>> of 2.164. Attempting to use an SSH keypair (with passphrase) to talk to
>>>>> BitBucket.org, in a Multibranch Pipeline job. The key is properly
>>>>> configured as an Private Key (entered manually) with a Passphrase.
>>>>>
>>>>> When I hit Scan Multibranch Pipeline Now, Jenkins immediately prompts
>>>>> the JVM's stderr for the passphrase. As an example:
>>>>>
>>>>> Enter passphrase for key '/tmp/ssh6766884284790436436.key':
>>>>>
>>>>> I also get an error in the Multibranch scan log:
>>>>>
>>>>>  > git ls-remote g...@bitbucket.org:group/repo.git # edited, of course
>>>>> ERROR: [Wed Apr 24 16:58:41 UTC 2019] Could not update folder level 
>>>>> actions from source 73a4292e-
>>>>> hudson.plugins.git.GitException: Command "git ls-remote 
>>>>> g...@bitbucket.org:group/repo.git" returned status code 128:
>>>>> stdout:
>>>>> stderr: Permission denied (publickey).
>>>>> fatal: Could not read from remote repository.
>>>>>
>>>>>
>>>>> This is bizarre. I'm running Ubuntu 16.04 using the default JRE. This
>>>>> did not happen on earlier versions of Jenkins that were running in Docker
>>>>> images - I had to remove Docker for VPN reasons.
>>>>>
>>>>> I'm basically off the air at this point. Did I just miss a plugin or
>>>>> do something silly?
>>>>>
>>>>> TIA,
>>>>> Randall
>>>>>
>>>> --
>>>> 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 jenkins...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-users/30f56e57-d3de-4e43-96dc-d07aa4ebdcda%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/30f56e57-d3de-4e43-96dc-d07aa4ebdcda%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>> --
>>> Thanks!
>>> 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/69755a15-a748-49e6-bb95-a9347afa75cc%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/69755a15-a748-49e6-bb95-a9347afa75cc%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtGJ98FZadZefQGXqySQAStwAHw_QayJN8Ueu_qmN57%2BVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.164 Prompting Terminal for Passphrase

[Mark Waite]

I've been using 2.164.1 and 2.164.2 since their release with both Java 8
and Java 11, alternating between various configurations, I'm confident the
update is not DOA.

I use bitbucket repositories that are secured with passphrase protected
private keys.  I use GitHub repositories that are secured with passphrase
protected private keys.  Check your configuration carefully.  Has the
passphrase protected private key been disabled in bitbucket?  Is Jenkins
reporting any issue with the private key format?

On Wed, Apr 24, 2019 at 12:53 PM Randall Becker 
wrote:

> I went back to try to use 2.164 on Docker and am experiencing similar
> issues. I wonder whether this update is DOA.
>
> On Wednesday, April 24, 2019 at 2:45:16 PM UTC-4, Mark Waite wrote:
>>
>>
>>
>> On Wed, Apr 24, 2019 at 12:35 PM Randall Becker 
>> wrote:
>>
>>> I should qualify... the passphrase prompt disappeared when setsid is
>>> used, but that still does not allow a passphrase-less keypair.
>>>
>>>
>> That may indicate that you have another problem.  If the passphrase
>> prompt disappeared, then ssh should have either completed the ssh
>> authentication or reported an error message.
>>
>>
>>> On Wednesday, April 24, 2019 at 2:33:07 PM UTC-4, Randall Becker wrote:
>>>>
>>>> The Multibranch Pipeline Plugin using JGit ends up incompatible.
>>>>
>>>>  > /usr/local/bin/jgit --version # timeout=10
>>>>  > /usr/local/bin/jgit ls-remote --symref 
>>>> g...@bitbucket.org:nonstop-git/nsgit.git # timeout=10
>>>>
>>>> ERROR: [Wed Apr 24 18:23:01 UTC 2019] Could not update folder level 
>>>> actions from source 0819144a...
>>>> hudson.plugins.git.GitException: Command "/usr/local/bin/jgit ls-remote 
>>>> --symref g...@bitbucket.org:group/repo.git" returned status code 1:
>>>> stdout:
>>>> stderr: fatal: "--symref" is not a valid option
>>>>
>>>> Looks like JGit (5.3.0 anyway) is no longer an option for polling. I'm
>>>> on Git Plugin 3.9.3.
>>>>
>>>> setsid made no difference.
>>>>
>>>> On Wednesday, April 24, 2019 at 2:24:00 PM UTC-4, Mark Waite wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Apr 24, 2019 at 12:10 PM Randall Becker wrote:
>>>>>
>>>>>> I'll bite. How can I use JGit instead of git in Jenkins? I thought it
>>>>>> was hard-burnt into the Git Plugin.
>>>>>>
>>>>>>
>>>>> In the "Global Tools Configuration" page of "Manage Jenkins", use the
>>>>> "Git" button and the "Add" button under it to add "jgit" as an
>>>>> implementation.  Once you've done that, then jobs will have an additional
>>>>> option to select which git implementation they will use.
>>>>>
>>>>>
>>>>>> On Wednesday, April 24, 2019 at 1:08:48 PM UTC-4, Randall Becker
>>>>>> wrote:
>>>>>>>
>>>>>>> This is a new situation that I have encountered after a clean
>>>>>>> install of 2.164. Attempting to use an SSH keypair (with passphrase) to
>>>>>>> talk to BitBucket.org, in a Multibranch Pipeline job. The key is 
>>>>>>> properly
>>>>>>> configured as an Private Key (entered manually) with a Passphrase.
>>>>>>>
>>>>>>> When I hit Scan Multibranch Pipeline Now, Jenkins immediately
>>>>>>> prompts the JVM's stderr for the passphrase. As an example:
>>>>>>>
>>>>>>> Enter passphrase for key '/tmp/ssh6766884284790436436.key':
>>>>>>>
>>>>>>> I also get an error in the Multibranch scan log:
>>>>>>>
>>>>>>>  > git ls-remote g...@bitbucket.org:group/repo.git # edited, of course
>>>>>>> ERROR: [Wed Apr 24 16:58:41 UTC 2019] Could not update folder level 
>>>>>>> actions from source 73a4292e-
>>>>>>> hudson.plugins.git.GitException: Command "git ls-remote 
>>>>>>> g...@bitbucket.org:group/repo.git" returned status code 128:
>>>>>>> stdout:
>>>>>>> stderr: Permission denied (publickey).
>>>>>>> fatal: Could not read from remote repository.
>>>>>>>
>>>>>>>

Re: Jenkins 2.164 Prompting Terminal for Passphrase

[Mark Waite]

On Wed, Apr 24, 2019 at 4:27 PM Randall Becker 
wrote:

> My docker image is doing fine, but the standalone Jenkins just won't
> authenticate with either JGit or git. It would be really nice to be able to
> do this without docker. Is there a standard launch recipe for my situation
> (in Ubuntu) or is SSH with passphrases just not available anymore?
>
>
If ssh with passphrases is not available anymore, that is a catastrophic
bug.  I'm reasonably confident that ssh with passphrases continues to be
available.  However, I won't be able to configure the test setup until
later this evening.  My Ubuntu 16 machine is busy right now running a
Docker image that would conflict with the native package install.



> java -jar jenkins.war
>
> doesn't cut it.
>
> :(
>
> On Wednesday, April 24, 2019 at 3:14:49 PM UTC-4, Randall Becker wrote:
>>
>> I'm rebuilding both docker and standalone images and will compare. The
>> docker image is fine with the key pair after I restarted it. I also had to
>> pick off the host signature using ssh -i blah g...@bitbucket.org... THEN
>> the docker image was able to authenticate. I'm going to try the same on the
>> standalone.
>>
>> On Wednesday, April 24, 2019 at 2:57:59 PM UTC-4, Mark Waite wrote:
>>>
>>> I've been using 2.164.1 and 2.164.2 since their release with both Java 8
>>> and Java 11, alternating between various configurations, I'm confident the
>>> update is not DOA.
>>>
>>> I use bitbucket repositories that are secured with passphrase protected
>>> private keys.  I use GitHub repositories that are secured with passphrase
>>> protected private keys.  Check your configuration carefully.  Has the
>>> passphrase protected private key been disabled in bitbucket?  Is Jenkins
>>> reporting any issue with the private key format?
>>>
>>> On Wed, Apr 24, 2019 at 12:53 PM Randall Becker 
>>> wrote:
>>>
>>>> I went back to try to use 2.164 on Docker and am experiencing similar
>>>> issues. I wonder whether this update is DOA.
>>>>
>>>> On Wednesday, April 24, 2019 at 2:45:16 PM UTC-4, Mark Waite wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Apr 24, 2019 at 12:35 PM Randall Becker 
>>>>> wrote:
>>>>>
>>>>>> I should qualify... the passphrase prompt disappeared when setsid is
>>>>>> used, but that still does not allow a passphrase-less keypair.
>>>>>>
>>>>>>
>>>>> That may indicate that you have another problem.  If the passphrase
>>>>> prompt disappeared, then ssh should have either completed the ssh
>>>>> authentication or reported an error message.
>>>>>
>>>>>
>>>>>> On Wednesday, April 24, 2019 at 2:33:07 PM UTC-4, Randall Becker
>>>>>> wrote:
>>>>>>>
>>>>>>> The Multibranch Pipeline Plugin using JGit ends up incompatible.
>>>>>>>
>>>>>>>  > /usr/local/bin/jgit --version # timeout=10
>>>>>>>  > /usr/local/bin/jgit ls-remote --symref 
>>>>>>> g...@bitbucket.org:nonstop-git/nsgit.git # timeout=10
>>>>>>>
>>>>>>> ERROR: [Wed Apr 24 18:23:01 UTC 2019] Could not update folder level 
>>>>>>> actions from source 0819144a...
>>>>>>> hudson.plugins.git.GitException: Command "/usr/local/bin/jgit ls-remote 
>>>>>>> --symref g...@bitbucket.org:group/repo.git" returned status code 1:
>>>>>>> stdout:
>>>>>>> stderr: fatal: "--symref" is not a valid option
>>>>>>>
>>>>>>> Looks like JGit (5.3.0 anyway) is no longer an option for polling.
>>>>>>> I'm on Git Plugin 3.9.3.
>>>>>>>
>>>>>>> setsid made no difference.
>>>>>>>
>>>>>>> On Wednesday, April 24, 2019 at 2:24:00 PM UTC-4, Mark Waite wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Apr 24, 2019 at 12:10 PM Randall Becker wrote:
>>>>>>>>
>>>>>>>>> I'll bite. How can I use JGit instead of git in Jenkins? I thought
>>>>>>>>> it was hard-burnt into the Git Plugin.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>

Re: Jenkins 2.164 Prompting Terminal for Passphrase

[Mark Waite]

On Wed, Apr 24, 2019 at 4:54 PM Mark Waite wrote:

>
>
> On Wed, Apr 24, 2019 at 4:27 PM Randall Becker  wrote:
>
>> My docker image is doing fine, but the standalone Jenkins just won't
>> authenticate with either JGit or git. It would be really nice to be able to
>> do this without docker. Is there a standard launch recipe for my situation
>> (in Ubuntu) or is SSH with passphrases just not available anymore?
>>
>>
> If ssh with passphrases is not available anymore, that is a catastrophic
> bug.  I'm reasonably confident that ssh with passphrases continues to be
> available.  However, I won't be able to configure the test setup until
> later this evening.  My Ubuntu 16 machine is busy right now running a
> Docker image that would conflict with the native package install.
>
>
I can't duplicate the problem you're seeing.  Steps I took while attempting
to duplicate the problem included:

   1. Create a passphrase protected RSA private key (no special characters
   in the passphrase, since the git client plugin is known to have issues with
   special characters in the passphrase)
   2. Register the public key of that passphrase protected RSA key with my
   account on bitbucket.org
   3. Update ~/.ssh/config so that ssh access to the bitbucket repository
   from my account 'mwaite' will use the newly created passphrase protected
   RSA private key
   4. Confirm that git clone from bitbucket.org prompts for the passphrase
   for that private key and fails if I do not provide that passphrase
   5. Confirm that git clone  from bitbucket.org prompts for the passphrase
   for that private key and succeeds when I provide the correct passphrase
   6. Install Jenkins 2.164.2 on a fully patched Ubuntu 16.04 machine using
   the instructions from
   https://jenkins.io/doc/book/installing/#debianubuntu.  I installed the
   recommended plugins from the installation wizard and made no other
   configuration changes (this installs and runs as the user 'jenkins', not
   the user 'mwaite')
   7. Define a Jenkins credential using the passphrase protected RSA
   private key
   8. Define a Jenkins freestyle job that clones a private repository.
   Confirm that without the credential, the job will not clone.  Confirm that
   with the credential, it clones as expected
   9. Enable JGit
   10. Reconfigure the freestyle job to use JGit instead of command line
   git as the implementation.  Confirm that with the credential, it clones as
   expected using JGit

As far as I can tell, passphrase protected private keys are working as
expected from Ubuntu 16.04 to bitbucket using either a Docker image (with
useSETSID=true) or the native package installation (with default value for
useSETSID).

Mark Waite


>
>
>> java -jar jenkins.war
>>
>> doesn't cut it.
>>
>> :(
>>
>> On Wednesday, April 24, 2019 at 3:14:49 PM UTC-4, Randall Becker wrote:
>>>
>>> I'm rebuilding both docker and standalone images and will compare. The
>>> docker image is fine with the key pair after I restarted it. I also had to
>>> pick off the host signature using ssh -i blah g...@bitbucket.org... THEN
>>> the docker image was able to authenticate. I'm going to try the same on the
>>> standalone.
>>>
>>> On Wednesday, April 24, 2019 at 2:57:59 PM UTC-4, Mark Waite wrote:
>>>>
>>>> I've been using 2.164.1 and 2.164.2 since their release with both Java
>>>> 8 and Java 11, alternating between various configurations, I'm confident
>>>> the update is not DOA.
>>>>
>>>> I use bitbucket repositories that are secured with passphrase protected
>>>> private keys.  I use GitHub repositories that are secured with passphrase
>>>> protected private keys.  Check your configuration carefully.  Has the
>>>> passphrase protected private key been disabled in bitbucket?  Is Jenkins
>>>> reporting any issue with the private key format?
>>>>
>>>> On Wed, Apr 24, 2019 at 12:53 PM Randall Becker 
>>>> wrote:
>>>>
>>>>> I went back to try to use 2.164 on Docker and am experiencing similar
>>>>> issues. I wonder whether this update is DOA.
>>>>>
>>>>> On Wednesday, April 24, 2019 at 2:45:16 PM UTC-4, Mark Waite wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Apr 24, 2019 at 12:35 PM Randall Becker 
>>>>>> wrote:
>>>>>>
>>>>>>> I should qualify... the passphrase prompt disappeared when setsid is
>>>>>>> used, but that still does not allow a passphrase-less keypair

Re: Jenkins 2.164 Prompting Terminal for Passphrase

[Mark Waite]

On Wed, Apr 24, 2019 at 6:30 PM Mark Waite 
wrote:

>
>
> On Wed, Apr 24, 2019 at 4:54 PM Mark Waite wrote:
>
>>
>>
>> On Wed, Apr 24, 2019 at 4:27 PM Randall Becker  wrote:
>>
>>> My docker image is doing fine, but the standalone Jenkins just won't
>>> authenticate with either JGit or git. It would be really nice to be able to
>>> do this without docker. Is there a standard launch recipe for my situation
>>> (in Ubuntu) or is SSH with passphrases just not available anymore?
>>>
>>>
>> If ssh with passphrases is not available anymore, that is a catastrophic
>> bug.  I'm reasonably confident that ssh with passphrases continues to be
>> available.  However, I won't be able to configure the test setup until
>> later this evening.  My Ubuntu 16 machine is busy right now running a
>> Docker image that would conflict with the native package install.
>>
>>
> I can't duplicate the problem you're seeing.  Steps I took while
> attempting to duplicate the problem included:
>
>1. Create a passphrase protected RSA private key (no special
>characters in the passphrase, since the git client plugin is known to have
>issues with special characters in the passphrase)
>2. Register the public key of that passphrase protected RSA key with
>my account on bitbucket.org
>3. Update ~/.ssh/config so that ssh access to the bitbucket repository
>from my account 'mwaite' will use the newly created passphrase protected
>RSA private key
>4. Confirm that git clone from bitbucket.org prompts for the
>passphrase for that private key and fails if I do not provide that
>passphrase
>5. Confirm that git clone  from bitbucket.org prompts for the
>passphrase for that private key and succeeds when I provide the correct
>passphrase
>6. Install Jenkins 2.164.2 on a fully patched Ubuntu 16.04 machine
>using the instructions from
>https://jenkins.io/doc/book/installing/#debianubuntu.  I installed the
>recommended plugins from the installation wizard and made no other
>configuration changes (this installs and runs as the user 'jenkins', not
>the user 'mwaite')
>7. Define a Jenkins credential using the passphrase protected RSA
>private key
>
> I failed to note one subtle value in the credential definition.  Since the
clone url provided by bitbucket is 'g...@bitbucket.org', I defined the
credential with the username 'git', not with my bitbucket username.  Since
my bitbucket username includes the '@' character (mark.earl.wa...@gmail.com),
it is not usable as the username portion of the repository URL  If the
previous version of git client plugin that you were running was before git
client plugin 2.7.3, then the credential may have worked even with the
wrong username in the credential.

There was a change made several versions of the git client ago to adapt to
a change in OpenSSH.  OpenSSH versions prior to 7.7 would accept an
incorrect value for the username and would then override that username with
the username that was embedded in the repository URL.  OpenSSH versions 7.7
and later fixed that OpenSSH bug.

The git client plugin had a dependency on that OpenSSH bug.  I don't think
that bug affects this case, since the OpenSSH version on Ubuntu 16.04 is
7.2, however, you can read about it at
https://issues.jenkins-ci.org/browse/JENKINS-50573

-- 
Thanks!
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/CAO49JtGH_Zwr-eQ-rkqn90YPVaWPqyHXN_qFttPOyVvADBq7zw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Under Jenkins SignTool Error "No certificates were found", works fine logged on as user

[Mark Waite]

On Thu, Apr 25, 2019 at 7:10 AM Hello Universe  wrote:

> How to use installed certificates from win8 using signtool?
>
>
Run the Windows agent from the Windows desktop rather than running it from
a service which has been allowed to interact with the desktop.  There seem
to be cases where programs run from services allowed to interact with the
desktop don't have the exact same capabilities as programs run from the
desktop.

Mark Waite


> On Thursday, August 27, 2015 at 10:51:29 PM UTC+8, Ed of the Mountain
> wrote:
>>
>> When I try to code sign in my Jenkins job I receive a SignTool error:
>>
>>
>> c:\jenkins\workspace\codesign-windows>
>>
>> signtool sign /t http://timestamp.digicert.com /n "Acme Inc." code.exe
>>
>> SignTool Error: No certificates were found that met all the given criteria.
>>
>>
>> I am using a DigiCert Extend Validation ( EV ) USB token that requires the 
>> USB token be connected to the build machine.  This works fine when logged on 
>> as normal user.
>>
>>
>>- I am running Jenkins as a Windows service.
>>- Service Log On is set to Local System account.
>>- Service is *allowed to interact with desktop.*
>>
>>
>>
>> When I logon as a normal user to the build machine, it works fine.
>>
>>
>> 1 - signtool sign /t http://timestamp.digicert.com /n "Acme Inc." code.exe
>>
>> 2 - This triggers a pop-up "Token Logon" dialog that requires user 
>> interaction
>>
>> 3 - I have a separate "Token Logon" watcher that finds the WIndows ID and 
>> enters password.
>>
>> 4 - Code is signed automatically
>>
>>
>> C:\jenkins\workspace\codesign-windows>signtool sign /t 
>> http://timestamp.digicert
>> .com /n "The Charles Machine Works, Inc." token-logon.exe
>> Done Adding Additional Store
>> Successfully signed: token-logon.exe
>>
>>
>> Any suggestions to try are much appreciated,
>>
>>
>> -Ed
>>
>> --
> 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/5c8ab94c-96ef-433d-9753-44336a67f2d5%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/5c8ab94c-96ef-433d-9753-44336a67f2d5%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtGEuESLQpVtO-XP9QwAies3w%3D0BV%2BNwt1MoWBLS%3DsyirA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

[Mark Waite]

Sorry, but no suggestions to offer on how to resolve that issue.

I would suggest that you host the Jenkins master on Linux or Windows and
run an agent on AIX.  Running the master on AIX probably places you in the
"less than 0.1% of all users" category.

On Thu, Apr 25, 2019 at 1:30 PM Rich Stephens  wrote:

> I have finally gotten Jenkins and the git plugin running (I have managed
> to upgrade to Java8).
>
> git works perfectly from the command line.
>
> If I include /opt/freeware/lib into the LIBPATH when starting jenkins,
> when I try to connect to a remove repository, I get basically this error:
>
> OpenSSL version mismatch. Built against 1000105f, you have 10bf
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
> Coincidentally, this is the same error that I get if I include
> /opt/freeware/lib in my own LIBPATH.
>
> If I _don't_ include /opt/freeware/lib in the LIBPATH for jenkins, I get:
>
> Failed to connect to repository : Command "git ls-remote -h ssh://
> g...@stash.saas-p.com:7999/optio/core.git HEAD" returned status code 255:
> stdout:
> stderr: exec(): 0509-036 Cannot load program git because of the following
> errors:
> 0509-150   Dependent module /usr/lib/libiconv.a(libiconv.so.2) could not
> be loaded.
> 0509-152   Member libiconv.so.2 is not found in archive
>
> If I don't include it in my own LIBPATH, git works normally.
>
> I tried reproducing my own PATH and LIBPATH in the startup script for git,
> but still no joy.  I get the second error.
>
>
> Obviously there is some sort of environment issue with jenkins, but I
> can't figure out what it is.
> Any thoughts?
>
>
>
>
>
>
>
> --
> 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/87b14e73-7fc1-49aa-b944-e227b473146c%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/87b14e73-7fc1-49aa-b944-e227b473146c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtH0kyvWKvTYGqJ9-GrZea1H7UkyBVrcH7t1Bccw3heJ0w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

[Mark Waite]

On Fri, Apr 26, 2019 at 6:06 AM Rich Stephens  wrote:

> I was thinking exactly the same thing.  I'd still have the same
> environment problem, either way.
>
>>
>>
You might, but you won't have git commands executed to scan multibranch
pipelines, since those are executed on the master.

I assume that adjusting the environment of the agent is simpler and faster
to test than adjusting the environment of the agent.

Running the master on Linux (or Windows) allows you to use the same JDK
that is used by many Jenkins users.  That will reduce the amount of code
that might detect problems in the IBM JDK on AIX.  It was a preventive
suggestion for future problems, with some distant hope that it might also
assist with this specific issue.


>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/86743ecd-4ee4-4bcb-8b4e-b80c1586b76c%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/86743ecd-4ee4-4bcb-8b4e-b80c1586b76c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEoXY%2B0HfKuH2MAMWW%3DU6W6G0X8h%2B1jyb376QWvaSMHpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

[Mark Waite]

On Fri, Apr 26, 2019 at 2:28 PM Rich Stephens  wrote:

> It was a bit of a joke.  I’m sorry if it offended you.
> It didn’t seem to offend anyone actually involved in the conversation, but
> thanks for the tip.
>
>
That was the point where I decided to stop responding to the thread.  You
seemed determined to proceed on the path that you had chosen.  That's your
right, since it is your time that you're investing in your exploration.

I am very interested to hear more about your experiences with Jenkins
masters on AIX.  While the JDK on AIX is JDK 1.8, I believe it is using the
IBM J9 virtual machine rather than the virtual machine provided by
OpenJDK.  I expect many interesting discoveries await you in that
exploration.  I'm aware of Jenkins agents on AIX and Jenkins agents on s390
mainframes (likely all running the IBM J9 virtual machine), but am not
aware of any other users running a Jenkins master on AIX.

If you're interested in the history of the J9 virtual machine, refer to
https://en.wikipedia.org/wiki/OpenJ9.  If you'd like to run a J9 virtual
machine on commodity hardware, refer to https://adoptopenjdk.net/ where you
can download an OpenJ9 based JDK.

If you'd like to join the Jenkins platform Special Interest Group, refer to
https://jenkins.io/sigs/platform/ .  We'd love to have your help as we work
with various platforms and explore various platforms.

Thanks!
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/900a6243-75d1-4cb4-bb75-63ee035e2335%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtG28aqSfe%3DwpEEgzJt5hhxFrrO4DmFq_m%3DOvg06p0E9cQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Odd environment problem with git under Jenkins on AIX

[Mark Waite]

On Tue, Apr 30, 2019 at 7:02 AM Rich Stephens wrote:


> I would be happy to join the platform group, though I am not sure of what
> assistance I might be.  While I have used Jenkins on Linux, AIX, HPUX, and
> Windows, my experience is limited to simple master setups building a legacy
> C/C++ project.
>
>
Anyone with the skills to maintain an aging AIX environment will certainly
be able to contribute when we're evaluating platform topics.  There are
often interesting subtleties in using Jenkins on a different platform that
can help the community as a whole.

Mark Waite


> Again, thank you for your assistance.
>
> --
> 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/c458b5e6-71aa-48a7-8fc9-cbdf4bcea6c6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/c458b5e6-71aa-48a7-8fc9-cbdf4bcea6c6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFu74PN8XW8ey_u4Wq4vP3BswFMRNv4XvrzhqU%2B52KhdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: scripted pipeline: bash: date -> MissingPropertyException: No such property: ... for class: groovy.lang.Binding

[Mark Waite]

On Thursday, May 2, 2019 at 6:35:58 AM UTC-6, b o b i wrote:
>
> Thank you, that work.
>
> Could you explain me why "\$" worked, i.e. where it is documented? (I lost 
> pretty much time with such "nonsense"). (a bash variable should be expanded 
> inside a bash script as $var or "${var}" etc., i.e. why in a bash, the vars 
> are not bashingly treated?)
>
>
The pipeline domain specific language is based on groovy.  Groovy does not 
expand variable references in strings surrounded by single quote characters 
(ASCII 0x27).  Groovy expands variable references in strings surrounded by 
double quote characters (ASCII 0x22).  A groovy variable reference in a 
string can have the same syntax as a bash variable reference.

Thus, your text:

sh """
  echo ${mytime}
"""

attempts to resolve the groovy variable 'mytime'.

If you had used:
sh '''
  echo ${mytime}
'''

it would attempt to resolve the shell variable 'mytime'.

See http://groovy-lang.org/syntax.html#_single_quoted_string and 
http://groovy-lang.org/syntax.html#_double_quoted_string for more details.

Mark Waite

 

> On Thursday, May 2, 2019 at 2:27:40 PM UTC+2, Daniel Butler wrote:
>>
>> Replace ${mytime} with \$mytime
>>
>> The mytime variable you've created is a bash one.
>>
>> Regards 
>> Daniel 
>>
>>
>> On Thu, 2 May 2019, 1:16 pm b o b i,  wrote:
>>
>>> Jenkins 2.174, in a scripted pipeline the following
>>>
>>> sh """#!/bin/bash
>>>echo "TTT"
>>>mytime="`date '+%Y_%m_%d__%H_%M_%S'`"
>>>echo ${mytime}
>>> """
>>>
>>> produces
>>>
>>> groovy.lang.MissingPropertyException: No such property: mytime for class: 
>>> groovy.lang.Binding
>>> at groovy.lang.Binding.getVariable(Binding.java:63)
>>> at 
>>> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:270)
>>> at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:289)
>>> at 
>>> org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:293)
>>> ...
>>>
>>> How can I have current time expanded as a string without the above error?
>>>
>>> -- 
>>> 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 jenkins...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/3b826017-27f1-45c9-925c-f396b13bcea9%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-users/3b826017-27f1-45c9-925c-f396b13bcea9%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> 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/34eb7130-cee0-4cab-be7e-dfffcd1fd572%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Under Jenkins SignTool Error "No certificates were found", works fine logged on as user

[Mark Waite]

On Wednesday, May 8, 2019 at 7:18:31 AM UTC-6, A M wrote:
>
> hi Mark
>
> I am struggling with a very similar issue. What exactly do you mean by 
> your comment and how do I achieve this?
>
>
I said:

> Run the Windows agent from the Windows desktop rather than running it 
from a service which has been allowed to interact with the desktop.

The most direct way to implement what I described is to:

   1. Login to the Windows desktop machine where code signing will be run
   2. Open a web browser to the Jenkins server
   3. Create an agent (a node) to represent that Windows computer
   4. Configure the agent to "Launch agent via Java Web Start"
   5. Define the required agent fields (like a remote root directory - I 
   prefer 'C:\J\' to reduce problems with Windows and long paths) and save the 
   configuration of that agent
   6. Download the 'agent.jar' file from the hyperlink on the web page, 
   save it somewhere convenient (like C:\J\agent.jar)
   7. Open a command prompt window on the Windows desktop machine and 
   change to the convenient directory C:\J
   8. Copy the 'Run from agent command line" from the web page into the 
   command prompt window

Thanks for asking!
Mark Waite
 

> I want to run the signtool.exe together with the certificate on a USB 
> token as an AfterPublish job in Jenkins. Jenkins is running as admin. 
> Single sign-on is activated for the USB token. Running signtool.exe in the 
> admin console works, running the same command through Jenkins results in 
> the "No certificates were found that met all the given criteria." error.
>
> Any help is much appreciated. 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/41f90117-e810-4b47-864e-839fc444fb86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is major version 2 security vulnerabilities applicable for major version 1

[Mark Waite]

Yes, if the capability exists in that version, then it is likely affected.
Versions that old are not tested for vulnerabilities nor are security fixes
provided for them.

On Sun, May 12, 2019, 5:43 PM agiri  wrote:

> Hi,
>
> As per the Jenkins Security Advisory below I see it mentions Affected
> Version as :
>
> Affected Versions
> 
>
>- Jenkins weekly up to and including 2.171
>- Jenkins LTS up to and including 2.164.
>
>
> https://jenkins.io/security/advisory/2019-04-10/
>
>
> Does this mean it affects the Jenkins major version 1 as well . Eg:
> version  1.650 ?
>
> Thanks
> AG
>
> --
> 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/27fccb07-4365-44c4-a95d-5d5d1f87b1dd%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/CAO49JtFPR-PR-txNVEUMg7iG%3Dg%2BBnqF4bxX31v9Uq%3DO%3DB2p84A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Git scm fails to check the expected branch when another branch has the target branch name as a suffix

[Mark Waite]

The git plugin includes support for multiple remotes (origin, upstream,
downstream, etc.) and for multiple branches.  It includes guessing code for
those cases where a branch name is ambiguous (like 'develop' in a
repository which includes branches named 'develop', 'kassandra/develop',
and 'mwaite/develop'). in the context of multiple remotes or multiple
branch names.

You can often avoid the guessing by naming the branch precisely, as in
'origin/develop'.

Mark Waite

On Wed, May 15, 2019 at 1:18 PM James Robson 
wrote:

> I have a repo with a branch called ‘develop’ and another branch called
> ‘kassandra/develop’. I have created a pipeline job that is building on
> ‘develop’, set to trigger with the ‘GitHub hook trigger for GITScm
> polling’.
>
>
> I expect this job to run only when ‘develop’ is changed, however it is
> running on every commit to the repo. This seems to be because the scm
> polling logic is comparing the last built git hash to the git hash on
> ‘kassandra/develop’ (see excerpt of the polling log below).
>
>
> Is this behaviour expected? Is there a way to prevent these unwanted runs?
>
>
> Setup:
>
> Git plugin: 3.9.3
>
> git client plugin: 2.7.6
>
>
> Git poll log:
>
> [poll] Last Built Revision: Revision 576aad8bdbfbf422d6a98899fafe78cc095ebb81
>  (refs/remotes/origin/develop)
> 
> [poll] Latest remote head revision on refs/heads/kassandra/develop is: 
> a9b4791c65f1ed2f1dc5669501fbeee58323e11e
>
> --
> 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/b3d3df79-0ab9-4fd8-aeb7-1e70bc2e87ca%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/b3d3df79-0ab9-4fd8-aeb7-1e70bc2e87ca%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHFeWBYBcgjO9%2BX9HGp_YiaLEEr661-ysf2aFrx1cdgnA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins init groovy script to upload custom plugin

[Mark Waite]

On Wed, May 15, 2019 at 7:37 PM Nageswara Rao Palukuri Venkata <
pvnra...@gmail.com> wrote:

> How can we upload a custom plugin file using groovy init script?
> Is there any init groovy script is available to upload custom plugin
> veracode (
> https://tools.veracode.com/integrations/Jenkins/bin/veracode-jenkins-plugin.hpi)
> ?
>

I think you may be mixing terms in a way that needs more clarification
before someone can answer your question.

Since Veracode is a static analysis tool, I assume that you want to submit
your source code or a portion of your source code to Veracode for
analysis.  You should probably refer to the Veracode help site which
describes "Using the Veracode Jenkins Plugin
<https://help.veracode.com/reader/PgbNZUD7j8aY7iG~hQZWxQ/_4G8gT1rhWMgVVtCI1C57A>"..
That page seems to describe how you can use the Veracode plugin to submit
source code for analysis by Veracode.

I don't think you actually want an init groovy script, since they generally
only run when the system starts, not when a Jenkins job runs and not when
code is changed in a source code repository.

I don't think you are creating a Jenkins plugin, so I assume you don't want
to upload a custom plugin to Veracode.  I assume you are creating your own
product and you want to upload its source code to Veracode.

Let me know if I've made a wrong assumption somewhere in that list of
assumptions.


> --
> 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/df6be5c5-fc5d-4937-8690-c8012db8daaf%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/df6be5c5-fc5d-4937-8690-c8012db8daaf%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEyCZTKgoQ6FJoBXtZVZVohb4ve_wCuARJ2s8VFvBFcoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins init groovy script to upload custom plugin

[Mark Waite]

On Wed, May 15, 2019 at 8:08 PM Nageswara Rao Palukuri Venkata <
pvnra...@gmail.com> wrote:

> Hi,
>
> I am creating a Jenkins instance using init scripts. I am able to
> configure all the required custom tools, extension and able to configure
> the jobs related to my project. I want to install the Veracode plugin also
> using the init script.
>
> Looking for any init script (groovy) to install Veracode plugin in Jenkins.
>

That feels like a complicated way to manage plugins, but it appears that
others have done something similar in the past.  Refer to
https://stackoverflow.com/questions/31457623/jenkins-plugin-installation as
one possible source of help, or the
https://github.com/blacklabelops-legacy/jenkins/blob/master/imagescripts/initplugins.sh
<https://github.com/blacklabelops-legacy/jenkins/blob/master/imagescripts/initplugins.sh#L22>
which
that page references.

I've preferred to manage my Jenkins instances as Docker images so that I
can specify the plugins to be installed in either a plugins.txt file or in
the ref/plugins directory.  That seems simpler to me than writing groovy
script functions to perform plugin installations during startup.



> Thanks
> Nageswara Rao
>
> On Wed, May 15, 2019 at 9:46 PM Mark Waite 
> wrote:
>
>>
>> On Wed, May 15, 2019 at 7:37 PM Nageswara Rao Palukuri Venkata <
>> pvnra...@gmail.com> wrote:
>>
>>> How can we upload a custom plugin file using groovy init script?
>>> Is there any init groovy script is available to upload custom plugin
>>> veracode (
>>> https://tools.veracode.com/integrations/Jenkins/bin/veracode-jenkins-plugin.hpi)
>>> ?
>>>
>>
>> I think you may be mixing terms in a way that needs more clarification
>> before someone can answer your question.
>>
>> Since Veracode is a static analysis tool, I assume that you want to
>> submit your source code or a portion of your source code to Veracode for
>> analysis.  You should probably refer to the Veracode help site which
>> describes "Using the Veracode Jenkins Plugin
>> <https://help.veracode.com/reader/PgbNZUD7j8aY7iG~hQZWxQ/_4G8gT1rhWMgVVtCI1C57A>"..
>> That page seems to describe how you can use the Veracode plugin to submit
>> source code for analysis by Veracode.
>>
>> I don't think you actually want an init groovy script, since they
>> generally only run when the system starts, not when a Jenkins job runs and
>> not when code is changed in a source code repository.
>>
>> I don't think you are creating a Jenkins plugin, so I assume you don't
>> want to upload a custom plugin to Veracode.  I assume you are creating your
>> own product and you want to upload its source code to Veracode.
>>
>> Let me know if I've made a wrong assumption somewhere in that list of
>> assumptions.
>>
>>
>>> --
>>> 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/df6be5c5-fc5d-4937-8690-c8012db8daaf%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/df6be5c5-fc5d-4937-8690-c8012db8daaf%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> 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/CAO49JtEyCZTKgoQ6FJoBXtZVZVohb4ve_wCuARJ2s8VFvBFcoA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEyCZTKgoQ6FJoBXtZVZVohb4ve_wCuARJ2s8VFvBFcoA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> 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/CAPG8g7bgpx686UKjHaQsSv_

Re: Credentials "secret text" -> bash -> expect ?

[Mark Waite]

I'm accustomed to seeing variable references in groovy strings as
"${variablename}", while it seemed in your example you were referencing it
as "$variablename".  Is that an intentional difference, or accidental?

On Wed, May 15, 2019 at 9:14 PM b o b i  wrote:

> It is a single line secret, but it wont work :|
>
> On Wednesday, May 15, 2019 at 7:31:27 PM UTC+2, Ivan Fernandez Calvo wrote:
>>
>> If your secret is multiline, the secret text does not work as expected,
>> you could store the one line base64 value of your secret and decode it
>> before send it, it could work
>
> --
> 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/85dc81a4-6206-4286-9578-42f1bec2fcfb%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/85dc81a4-6206-4286-9578-42f1bec2fcfb%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHicbtPTDKPBWyMBcgjcXj%2BNNRqNJv3CpvrGj5AwCm1%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Git scm fails to check the expected branch when another branch has the target branch name as a suffix

[Mark Waite]

I don't know if it will help, but you could try replacing the "syntactic
sugar" command `git` with the `checkout` command.  Pipeline Syntax link on
the Pipeline pages will help get the correct syntax for the details of the
checkout command.

On Thu, May 16, 2019 at 7:25 AM James Robson 
wrote:

>
>
> On Wednesday, 15 May 2019 21:28:52 UTC+1, Mark Waite wrote:
>>
>>
>> You can often avoid the guessing by naming the branch precisely, as in
>> 'origin/develop'.
>>
>
> I attempted to use 'origin/develop' as the branch name, but that causes
> the job to fail the checkout with "ERROR: Couldn't find any revision to
> build. Verify the repository and branch configuration for this job". Here's
> the pipeline I'm testing this with:
>
> node('linux') {
> stage('checkout') {
> git branch: 'origin/develop', ...
> }
> }
>
> The last line of output before the failure is a 'git fetch' call which is
> identical to a run using a branch name of 'develop' which will then
> checkout successfully.
>
> --
> 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/f03ac832-bad1-42cb-8840-ce0cb632ae21%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/f03ac832-bad1-42cb-8840-ce0cb632ae21%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtG%3D8AgjqrXmZpAHBsKPr6Ep7A-ZV%2BEfTGroc46VZB%3DvVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Securing build scripts when building pull requests

[Mark Waite]

The pipeline library on ci.jenkins.io is a good example of a library
written to safely handle pull requests which might be malicious.  Refer to
isTrusted
<https://github.com/jenkins-infra/pipeline-library/blob/master/README.adoc#infraistrusted>
and how it is used to safeguard operations.

I believe ci.jenkins.io jobs are also configured to not allow Jenkinsfile
to be used from the target branch even for pull requests.  That avoids the
risk of a pull request submitted which executes a malicious Jenkinsfile.

On Fri, May 17, 2019 at 1:03 AM Simon Richter 
wrote:

> Hi,
>
> On Thu, May 16, 2019 at 12:11:54PM -0700, Christopher Weaver wrote:
>
> > For a project I work on, we have set up Jenkins, using the GitHub Branch
> > Source Plugin, to do automatic builds for pushes to our repository,
> > including test builds for pull requests. This is all working, but I am
> > concerned about the security implications for the pull requests.
>
> Yes, that is a common problem. Most people either only test pull requests
> from trusted people, or configure Jenkins to test inside a container with
> no network access and strict resource limits that is discarded after the
> build.
>
>Simon
>
> --
> 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/20190517080348.GA17598%40psi5.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHAT5tbH9%3Df%2BZEYJ%3DsO-6RisYM0spTQH9PKgu31WMCpmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: node parameter makes pipeline fail even if it's unused

[Mark Waite]

On Thu, May 16, 2019 at 7:13 AM gbon  wrote:

> Hi All,
> Asking for advice on this weird behavior:
>
> I have a (declarative) pipeline that works perfectly fine and selects the
> agent like so
>
> pipeline {
>   agent {
> node {
>   label "SOME_LABEL"
> }
>   }
>   ...
> }
>
> If I edit the pipeline configuration to add a parameter of type Node (
> which I'm still not using in the pipeline! )  the pipeline fails
> immediately with the following error
>
> Caused by: hudson.plugins.git.GitException: Command "git fetch --tags 
> --progress g...@my-super-secret-gitlab-repository.git 
> +refs/heads/*:refs/remotes/origin/*" returned status code 128:
> stdout:
> stderr: Could not create directory '/export/homes/my_user/.ssh'.
> Host key verification failed.
> fatal: Could not read from remote repository.
>
>
>
> That I think has nothing to do with git since it works perfectly fine and
> the label is still hardcoded.
> Seems like the job isn't correctly dispatched or something but I can't
> figure out what's happening.
>
>
The declarative Pipeline includes an implicit checkout of the repository on
each agent that will be performing a step.  When you add the `node` step,
declarative Pipeline attempts to perform a checkout on that node.  If you
don't need that default checkout, the `skipDefaultCheckout` option is
available.

If you need that default checkout, then you probably need to fix the file
system permissions of the /export/homes/my_user/.ssh directory so that the
user executing the Pipeline job can read the .$HOME/.ssh directory.
Command line git uses `ssh` to authenticate and clone repositories using
the secure shell protocol.

If the `/export/homes/my_user` directory is accessed over NFS, then you may
also need to assure that the agent process is not running as root. Root
access over NFS is usually not allowed.

You could check for those types of conditions in your environment with a
Jenkinsfile something like this:

pipeline {
  options {
skipDefaultCheckout()
  }
  agent {
node {
  label "!windows"
}
  }
  stages {
stage('Report username') {
  steps {
sh 'id'
  }
}
  }
}



> 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/0f7c8c1c-c1a8-4495-8be5-d00b5c5997ff%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/0f7c8c1c-c1a8-4495-8be5-d00b5c5997ff%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFqxh-mHCxnLK_Rs-3WgXVkZWR8urCnPQ3k52pVDyzLRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: node parameter makes pipeline fail even if it's unused

[Mark Waite]

I failed to mention that performing git operations over NFS is much slower
than performance those operations with a local file system.  I'd generally
recommend that file systems on static agents should be locally attached
file systems rather than network file systems if possible.

On Fri, May 17, 2019 at 4:59 AM Mark Waite 
wrote:

>
>
> On Thu, May 16, 2019 at 7:13 AM gbon  wrote:
>
>> Hi All,
>> Asking for advice on this weird behavior:
>>
>> I have a (declarative) pipeline that works perfectly fine and selects the
>> agent like so
>>
>> pipeline {
>>   agent {
>> node {
>>   label "SOME_LABEL"
>> }
>>   }
>>   ...
>> }
>>
>> If I edit the pipeline configuration to add a parameter of type Node (
>> which I'm still not using in the pipeline! )  the pipeline fails
>> immediately with the following error
>>
>> Caused by: hudson.plugins.git.GitException: Command "git fetch --tags 
>> --progress g...@my-super-secret-gitlab-repository.git 
>> +refs/heads/*:refs/remotes/origin/*" returned status code 128:
>> stdout:
>> stderr: Could not create directory '/export/homes/my_user/.ssh'.
>> Host key verification failed.
>> fatal: Could not read from remote repository.
>>
>>
>>
>> That I think has nothing to do with git since it works perfectly fine and
>> the label is still hardcoded.
>> Seems like the job isn't correctly dispatched or something but I can't
>> figure out what's happening.
>>
>>
> The declarative Pipeline includes an implicit checkout of the repository
> on each agent that will be performing a step.  When you add the `node`
> step, declarative Pipeline attempts to perform a checkout on that node.  If
> you don't need that default checkout, the `skipDefaultCheckout` option is
> available.
>
> If you need that default checkout, then you probably need to fix the file
> system permissions of the /export/homes/my_user/.ssh directory so that the
> user executing the Pipeline job can read the .$HOME/.ssh directory.
> Command line git uses `ssh` to authenticate and clone repositories using
> the secure shell protocol.
>
> If the `/export/homes/my_user` directory is accessed over NFS, then you
> may also need to assure that the agent process is not running as root. Root
> access over NFS is usually not allowed.
>
> You could check for those types of conditions in your environment with a
> Jenkinsfile something like this:
>
> pipeline {
>   options {
> skipDefaultCheckout()
>   }
>   agent {
> node {
>   label "!windows"
> }
>   }
>   stages {
> stage('Report username') {
>   steps {
> sh 'id'
>   }
> }
>   }
> }
>
>
>
>> 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/0f7c8c1c-c1a8-4495-8be5-d00b5c5997ff%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/0f7c8c1c-c1a8-4495-8be5-d00b5c5997ff%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Thanks!
> Mark Waite
>


-- 
Thanks!
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/CAO49JtGDDQkNQ72h5VyzhRO2_2GYfimE%3Da8UdVDo4aLW%3Di8yjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Windows Master and Linux Slave give an error: Cannot run program "C:\Windows\system32\cmd.exe"

[Mark Waite]

If you'd like labels assigned automatically to your agents, install
the "Platform
Labeler Plugin <https://plugins.jenkins.io/platformlabeler>".

If the labels assigned by the platform labeler plugin are not generic
enough, install the "Implied Labels Plugin
<https://plugins.jenkins.io/implied-labels>" and you can define that all
agents with the label "CentOS" should also be assigned the label "linux"
(as an example).  It simplifies the management of labels.

If you'd like an example implied labels definition for various Linux
operating systems, I have one in my docker repository
<https://github.com/MarkEWaite/docker-lfs/blob/4a9773f22066c9db6fa7841fcbcfb14dacd26918/ref/org.jenkinsci.plugins.impliedlabels.Config.xml#L8>
.

On Mon, May 20, 2019 at 6:18 AM Bob TheBuilder 
wrote:

> Hi Gregory,
>
> what kind of Jenkinsfile do you use? Scripted or declarative?
> In scripted, you would enclose your sh in a
>
>> node('linux_label') {
>> sh "your shell script"
>> }
>
>
> , on declarative, use
> stage ("Run on Linux only") {
>agent { label "linux_label" }
>steps {
>script {
>  sh "you shell script"
>}
> }
>
>  with agent('linux_label'). Linux label would be a label you attached to
> the Linux slave/node
>
> --
> 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/e81a95b4-d8a4-4fa0-931a-f314e9616796%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/e81a95b4-d8a4-4fa0-931a-f314e9616796%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFJYtp5ZGSCnKmGAMbJt%2BOtg%3DXAT9jBN%3D-KRY8aQDoWig%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins replaces all occurrences of my user name in the log with asterisks. How can I change that?

[Mark Waite]

On Tue, May 21, 2019 at 5:24 AM Tim Jaacks  wrote:

> While this makes sense for actual occurrences (i.e. where the asterisk'ed
> text REALLY is my user name), it is quite counterproductive in situations
> where the user name accidentally matches some other strings in the log.
>
> For example, my user name I use in the credentials is "jenkins" (oh yeah,
> creative). Everywhere this name is used (e.g. in URLs like
> jenk...@myserver.de/somepath) it is correctly masked (showing @
> myserver.de/somepath).
> However, I have a script called "jenkins_patches.sh" which is called
> during the build. This gets logged as "_patches.sh", which is quite
> ridicoulous, because the credentials are not actually used here.
> Furthermore, my Jenkins instance is hosted under some URL like "
> http://mycompanyintranet/jenkins";, resulting in "
> http://mycompanyintranet/";, which makes all URLs in my build log
> unusable. This is quite annoying.
>
> Is there a solution to change this?
>

The only solution that I am aware of is to not use the plugin that masks
usernames and passwords.  If you use the Jenkins credentials plugin and
provide all your credentials through the credentials plugin, you generally
should not need to mask references to usernames and generally won't show
passwords in the log files (or elsewhere).

> --
> 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/dc508f41-cd5b-449b-a0d4-11d9aa5c2668%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/dc508f41-cd5b-449b-a0d4-11d9aa5c2668%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFDvenvJ16ZE15XBkLRnxzL%2BkYmekdsFzMpgy4s%2BjErwg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins replaces all occurrences of my user name in the log with asterisks. How can I change that?

[Mark Waite]

Based on https://issues.jenkins-ci.org/browse/JENKINS-44860 , it appears to
be the credentials binding plugin.  Sorry for my misdirection.

On Tue, May 21, 2019 at 5:36 AM Tim Jaacks  wrote:

> Thanks for your reply, Mark. I am using the credentials plugin to provide
> the stated credentials and I thought, that it is actually this plugin which
> performs the masking. If not, which plugin does this? I did not find any
> installed plugins in my instance which seem to do this.
>
> Am Dienstag, 21. Mai 2019 13:27:50 UTC+2 schrieb Mark Waite:
>>
>> The only solution that I am aware of is to not use the plugin that masks
>> usernames and passwords.  If you use the Jenkins credentials plugin and
>> provide all your credentials through the credentials plugin, you generally
>> should not need to mask references to usernames and generally won't show
>> passwords in the log files (or elsewhere).
>>
> --
> 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/5c846913-65ef-41b2-a470-1f305ac27f75%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/5c846913-65ef-41b2-a470-1f305ac27f75%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtG3dWN_DvT6xx8GGCTczaDLVt%3DsTbzK1MAemCUXMzjX4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins replaces all occurrences of my user name in the log with asterisks. How can I change that?

[Mark Waite]

On Tue, May 21, 2019 at 7:26 AM Tim Jaacks  wrote:

> Thanks very much for the link. That is indeed exactly my issue.
>
> Is there an alternative to using the credentials binding plugin? I need
> the credentials to be inserted into an URL within the test script. How can
> I do this without the credentials binding plugin?
>

I don't know of a way to do that.

If it would work in your environment, you might consider switching to use a
different account to run the Jenkins agent than the account that provides
the credentials.  That's an ugly work around but may avoid many of the
problems.


>
> Am Dienstag, 21. Mai 2019 14:48:57 UTC+2 schrieb Mark Waite:
>>
>> Based on https://issues.jenkins-ci.org/browse/JENKINS-44860 , it appears
>> to be the credentials binding plugin.  Sorry for my misdirection.
>>
> --
> 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/e9881260-2c05-41eb-bf22-b4e17d58e70f%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/e9881260-2c05-41eb-bf22-b4e17d58e70f%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFnKWmq-xNMMSZQgTeA36kWjNnoZZ9%2BRPMF1mnGbP0P2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Branch API Failed Update

[Mark Waite]

Not with branch api plugin, though I have seen those messages in the past.
They typically resolved themselves within a few hours after initial release
of the plugin.

On Tue, May 21, 2019 at 9:03 AM Steven Wall <
steve.w...@primetimesoftware.com> wrote:

> Hello,
>
> Is anyone else seeing this error when trying to update “Branch API”?
>
> Best,
>
> Steve
>
>
>
> java.io.FileNotFoundException:
> http://archives.jenkins-ci.org/plugins/branch-api/2.5.0/branch-api.hpi
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1890)
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:3051)
>
> at
> java.net.URLConnection.getHeaderFieldLong(URLConnection.java:629)
>
> at
> java.net.URLConnection.getContentLengthLong(URLConnection.java:501)
>
> at java.net.URLConnection.getContentLength(URLConnection.java:485)
>
> at
> hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1158)
>
> Caused: java.io.FileNotFoundException:
> http://archives.jenkins-ci.org/plugins/branch-api/2.5.0/branch-api.hpi
>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
>
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>
> at
> sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1944)
>
> at
> sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1939)
>
> at java.security.AccessController.doPrivileged(Native Method)
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1938)
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1508)
>
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
>
> at
> hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1174)
>
> Caused: java.io.IOException: Failed to load
> http://updates.jenkins-ci.org/download/plugins/branch-api/2.5.0/branch-api.hpi
>  to /var/jenkins_home/plugins/branch-api.jpi.tmp
>
> at
> hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1181)
>
> Caused: java.io.IOException: Failed to download from
> http://updates.jenkins-ci.org/download/plugins/branch-api/2.5.0/branch-api.hpi
>  (redirected to:
> http://archives.jenkins-ci.org/plugins/branch-api/2.5.0/branch-api.hpi)
>
> at
> hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1215)
>
> at
> hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1752)
>
> at
> hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:2015)
>
> at
> hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1726)
>
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>
> at
> hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:112)
>
> at java.lang.Thread.run(Thread.java:748)
>
>
>
> --
> 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/1f76738a-02d6-4842-b542-0f21e84e38ba%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/1f76738a-02d6-4842-b542-0f21e84e38ba%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFWdBmzEB1pfg%3DoyDmCDas0nHwjLA4-7WKEXzVYQY_4Ag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: multibranch pipeline & checkout over shh & permission denied

[Mark Waite]

Submodule authentication in the git plugin and git client plugin requires
that the same protocol must be used for the parent repository and the
submodules.  Different credential methods are required to provide command
line git with http/https credentials than with ssh credentials.  A mix of
the two in a single repository definition would require much more
sophisticated operations from the git plugin than it is currently able to
perform.

If the submodules and the parent repo are all using the same protocol (ssh
or http), then you may need to enable the checkbox which causes the git
plugin to use credentials with submodule operations.  I believe it is
disabled by default.


On Thu, May 23, 2019 at 5:37 AM Ewelina Wilkosz  wrote:

> I have a pipelineJob where I use ssh to clone repository and configured
> credentials, let's call it X, are working great
>
> I also have a multibranch pipeline, where I configured "Checkout over SSH"
> and select same X credentials, but I can't clone
> I get
>
> ERROR: Error fetching remote repo 'origin'
> [...]
> stderr: Permission denied (public key)
> fatal: Could not read from remote repository
>
> The same user could clone via https, but there are some submodules
> configured via ssh, so I need ssh working...
>
> Any ideas?
>
> --
> 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/89f8e2a2-6082-4642-90ac-31f8da684c06%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/89f8e2a2-6082-4642-90ac-31f8da684c06%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtF8g3UCfGuqr02roM4HBkOhQgqVxA7T7nwRRtWBawMwOA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: multibranch pipeline & checkout over shh & permission denied

[Mark Waite]

You might double check that the private key credential you're using with
that checkout does not use a passphrase, or if it uses a passphrase, does
not include any shell special characters in the passphrase.  There is a
known bug in the git client plugin handling of ssh passphrases with shell
special characters.

You might also double check that the private key you're using is recognized
by both agent and server.  I've generated ed25519 private keys in the past
only to discover that they were not recognized on one or more of the old
systems that I needed to support.  I will be surprised if that is the case
here, since that usually has a different error message, but it is worth
checking.

On Thu, May 23, 2019 at 6:57 AM Ewelina Wilkosz  wrote:

> I see,
>
> but in my case I don't event get to submodules. multibranch pipeline fails
> on checking out main repo via ssh - I use checkout over SSH option - when a
> regular pipelineJob has no trouble with ssh
>
> On Thursday, May 23, 2019 at 2:44:23 PM UTC+2, Mark Waite wrote:
>>
>> Submodule authentication in the git plugin and git client plugin requires
>> that the same protocol must be used for the parent repository and the
>> submodules.  Different credential methods are required to provide command
>> line git with http/https credentials than with ssh credentials.  A mix of
>> the two in a single repository definition would require much more
>> sophisticated operations from the git plugin than it is currently able to
>> perform.
>>
>> If the submodules and the parent repo are all using the same protocol
>> (ssh or http), then you may need to enable the checkbox which causes the
>> git plugin to use credentials with submodule operations.  I believe it is
>> disabled by default.
>>
>>
>> On Thu, May 23, 2019 at 5:37 AM Ewelina Wilkosz 
>> wrote:
>>
>>> I have a pipelineJob where I use ssh to clone repository and configured
>>> credentials, let's call it X, are working great
>>>
>>> I also have a multibranch pipeline, where I configured "Checkout over
>>> SSH" and select same X credentials, but I can't clone
>>> I get
>>>
>>> ERROR: Error fetching remote repo 'origin'
>>> [...]
>>> stderr: Permission denied (public key)
>>> fatal: Could not read from remote repository
>>>
>>> The same user could clone via https, but there are some submodules
>>> configured via ssh, so I need ssh working...
>>>
>>> Any ideas?
>>>
>>> --
>>> 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 jenkins...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/89f8e2a2-6082-4642-90ac-31f8da684c06%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/89f8e2a2-6082-4642-90ac-31f8da684c06%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> 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/a7a0bb7c-4b82-4f7f-b57e-29b9ff210f3e%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/a7a0bb7c-4b82-4f7f-b57e-29b9ff210f3e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHaSC6QF%2Bfi%3DUp%2BLVKm4ViK_%3DiaaNwMcdXFhZq9wDvcYA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline with multiple Git repositories - how to checkout?

[Mark Waite]

Git takes full control of the directory for each checkout.  Thus, the last
checkout "wins" by containing the content of only that checkout.

Perform a checkout command for each repository in a separate directory.
Create the directory for each checkout with the dir() step or the ws()
step, and place the checkout inside the block from that step.  Something
like this:

dir('dir-1-for-repo-1') {
  checkout([$class: 'GitSCM', branches: [[name: gitBranch]], extensions: [[
$class: 'CloneOption', timeout: 120]],
  userRemoteConfigs: [[credentialsId: "${credentialsId}", url:
mainProjectGITURL ]  ]])
}
dir('dir-2-for-repo-2') {
  checkout([$class: 'GitSCM', branches: [[name: gitBranch]], extensions: [[
$class: 'CloneOption', timeout: 120]],
  userRemoteConfigs: [[credentialsId: "${credentialsId}", url:
list[0] ]  ]])
}

On Tue, May 28, 2019 at 4:14 AM Jacques van der Merwe 
wrote:

> I know this is fairly old thread but I have an issue
> when using the multi repo checkout it seems to remove the previous repo
> checkout before doing the new one.
> I have tried checking all the repos required for my build using the
> Jenkins Declarative "checkout" command
> checkout([$class: 'GitSCM', branches: [[name: "${gitBranch}"]],
> doGenerateSubmoduleConfigurations: false, extensions: [[$class:
> 'CloneOption', timeout: 120]], submoduleCfg: [], userRemoteConfigs: [
>  [credentialsId: "${credentialsId}", url: "${mainProjectGITURL}"],
>  [credentialsId: "${credentialsId}", url: "${list[0]}"],
>  [credentialsId: "${credentialsId}", url: "${list[1]}"],
>  [credentialsId: "${credentialsId}", url: "${list[2]}"],
>  [credentialsId: "${credentialsId}", url: "${list[3]}"]
>  ]])
> With this config I can see on my build server each project are being
> checked out but only the last project is availbale after this checkout.
>
>
Multiple userRemoteConfigs in a single checkout command will perform a
single checkout of one of the remote configs.  It won't iterate over the
list of remote configs and definitely won't create the separate
subdirectories that would be needed to retain a checkout of multiple
repositories.

Multiple userRemoteConfigs in a single checkout are allowed as a historical
use that was allowed for those rare cases where multiple locations
contained the same repository and any one of the repositories could be
used.  Multiple userRemoteConfigs won't help in this case and they don't
help in almost all cases.


> I also tried doing in a loop using "git" only
>def list = "${includedProjectsGITURLS}".split("\n")
> echo "Number of repos : " + list.size()
> echo "Checking out main project (${gitBranch}) :  " +
> mainProjectGITURL + "\n";
> git credentialsId: 'blablabla', url: "${mainProjectGITURL}"
> for (String gitSubURL:list)
>  {
> echo "Checking out sub project (${gitBranch}) :  " + gitSubURL + "\n";
> git credentialsId: 'blablabla', url: "${gitSubURL}"
>  }
> The result is the same, making me think "checkout" is just wrapper for GIT
>
>
The git step is a simplified form of the checkout step.  If your case does
not need the full capability of the checkout step, you are welcome to use
the git step.  I find that I almost always want the checkout step because
it allows me to control things more precisely.


> I also tried checking each repo into its own sub folder but the result is
> the same
>
>
We'll need more explanation of what was tried in this case, since that is
the technique that works for many users.

Thanks,
Mark Waite


> any ideas how I can checkout multiple repos in Jenkins declarative script
> for single build
>
>
>
> On Wednesday, December 21, 2016 at 7:25:43 PM UTC+2, Torsten Reinhard
> wrote:
>>
>> Hi,
>>
>> I have a pipeline doing a build and afterwards a deployment to the TEST
>> environment.
>>
>> For the build I need to
>> // checkout sources for building
>> checkout scm
>>
>> and later on I need to
>> //checkout configuration for TEST environment
>> checkout scm (config)
>>
>> I wasn´t able to configure a working directory for each repo - and the
>> "Multiple SCMs plugin" is deprecated with a hint to the Pipeline plugin.
>> How can I setup the Pipeline job so it´s using "Pipeline script from SCM"
>> AND additionally some files/configs from a different repo?
>>
>> I know about the workaround wi

Re: Failed ANT build: Unable to locate tools.jar

[Mark Waite]

I suspect that something (Jenkins tool definition, local setting on the
computer, etc.) is defining a JAVA_HOME environment variable as  c:\Program
Files\Java\jre1.8.0_201.

Add a bat step to the job prior to calling `ant` and run the command
`set`.  That will report the environment variable to confirm the guess that
something is placing value that into the environment.

On Fri, Jun 7, 2019 at 8:49 AM ABostonGal ABostonGal 
wrote:

> I have an ANT build that has been working just fine for quite a while and
> suddenly it has stopped working and I am trying to figure out why. Here is
> what the Jenkins console displays and my notes about it. I've obscure the
> actual site name, directory values, and Jenkins job name, etc. "uvwx" is
> the Jenkins job that is failing to build
>
> In Jenkins console:
>
> No changes for svn://ab/cd/ef/gh/ijk since the previous build
>
> Copied 3 artifacts from "lmnop" build number 137
>
> Copied 2 artifacts from "qrst" build number 2700
>
> [uvwx] $ cmd.exe /C
> "C:\Users\jenkins\jenkins_home\tools\hudson.tasks.Ant_AntInstallation\Ant_1.9.6\bin\ant.bat
> get-revision compile-tests compile-javadoc package-jar package-javadoc &&
> exit %%ERRORLEVEL%%"
> Unable to locate tools.jar. Expected to find it in C:\Program
> Files\Java\jre1.8.0_201\lib\tools.jar
>
>
> My notes about this:
>
> What I want to know is: WHY does the build "expect" to find it in
> "c:\Program Files\Java\jre1.8.0_201"? There IS no such path on the machine
> on which the job is building...
>
> How can I find out WHERE that value is coming from? I've been looking at
> the ant, build files and source code and don't see where that value would
> be set.
>
> 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/794e1399-0d52-42d9-b805-0e197667d3c6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/794e1399-0d52-42d9-b805-0e197667d3c6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEjQTsh2fgCNtBP5PNcM_%3DbCBBpq0XGWExob6%3D7sv9yBg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed ANT build: Unable to locate tools.jar

[Mark Waite]

Most interesting.

Ant expects to have a full JDK available.  It depends on the tools.jar file
which is provided by the JDK but is not available with the JRE.  The
directory name "jre1.8.0_201" indicates that it is not a JDK, but a JRE.
You indicated that even that directory does not exist on the agent running
the build.  It might also indicate that the job is running on a Windows
agent that has the Oracle script in its path which attempts to dynamically
determine the path to the Java program.

The path that is being used to run ant indicates that you have a Jenkins
build tool defined for Ant 1.9.6.  That may indicate you also have a JDK
tool defined for JRE 1.8.0_201.  The Jenkins tool definitions are available
from the "Configure System" page and might help detect the source of the
jre1.8.0_201 setting.

Best of luck!
Mark Waite

On Fri, Jun 7, 2019 at 12:44 PM ABostonGal ABostonGal 
wrote:

> Thank you Mark. Yes, I checked for that the Environment Variables but
> unfortunately: nothing! I've tried adding a JAVA_HOME variable pointing to
> the place where the tools.jar is and the build failed.
> I'd really like to understand how the build files "think" they should be
> looking for this before I do anymore "experimenting"...
>
>
> On Friday, June 7, 2019 at 10:48:58 AM UTC-4, ABostonGal ABostonGal wrote:
>>
>> I have an ANT build that has been working just fine for quite a while and
>> suddenly it has stopped working and I am trying to figure out why. Here is
>> what the Jenkins console displays and my notes about it. I've obscure the
>> actual site name, directory values, and Jenkins job name, etc. "uvwx" is
>> the Jenkins job that is failing to build
>>
>> In Jenkins console:
>>
>> No changes for svn://ab/cd/ef/gh/ijk since the previous build
>>
>> Copied 3 artifacts from "lmnop" build number 137
>>
>> Copied 2 artifacts from "qrst" build number 2700
>>
>> [uvwx] $ cmd.exe /C
>> "C:\Users\jenkins\jenkins_home\tools\hudson.tasks.Ant_AntInstallation\Ant_1.9.6\bin\ant.bat
>> get-revision compile-tests compile-javadoc package-jar package-javadoc &&
>> exit %%ERRORLEVEL%%"
>> Unable to locate tools.jar. Expected to find it in C:\Program
>> Files\Java\jre1.8.0_201\lib\tools.jar
>>
>>
>> My notes about this:
>>
>> What I want to know is: WHY does the build "expect" to find it in
>> "c:\Program Files\Java\jre1.8.0_201"? There IS no such path on the machine
>> on which the job is building...
>>
>> How can I find out WHERE that value is coming from? I've been looking at
>> the ant, build files and source code and don't see where that value would
>> be set.
>>
>> 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/bd6b7015-91fa-4e87-9543-2b6b4f3d4b4d%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/bd6b7015-91fa-4e87-9543-2b6b4f3d4b4d%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFPCH36rHw8_ip94KFaxf9u-GO-4TTnXEL39R_M41mx6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: gitSCM failed after updates

[Mark Waite]

al behaviour that GitSCM generates and
> tries to run a random-named bat file?  It's unclear to me if the bat file 
> isn't created or is unreadable, although Jenkins is running
> as SYSTEM and has generally been able to read and write everything.
>
> Does anyone have any thoughts on what may have gone wrong?
>
>  -
>
>
> The updates made Friday night:
>
> >>> Artifactory 3.2.2 -> 3.2.4  [ security warning
> ]
> >>> Pipeline: API 2.34 ->
> 2.35
> >>> Pipeline: Basic Steps 2.16 ->
> 2.18
> >>> Pipeline: Declarative 1.3.8 ->
> 1.3.9
> >>> Pipeline: Declarative Extension Points API 1.3.8 ->
> 1.3.9
> >>> Pipeline: Groovy 2.69 ->
> 2.70
> >>> Pipeline: Model API 1.3.8 ->
> 1.3.9
> >>> Pipeline: Nodes and Processes 2.30 ->
> 2.31
> >>> Pipeline: SCM Step 2.7 ->
> 2.9
> >>> Pipeline: Stage Tags Metadata 1.3.8 ->
> 1.3.9
> >>> Pipeline: Step API 2.19 ->
> 2.20
> >>> Slack Notification 2.23 -> 2.24
>
> I've since rolled back all of the "Pipeline: ..." changes.  The problem
> didn't change.
>
> About 40 Cygwin updates (I didn't enumerate those.)
>
> --
> 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/2d7c0927-22ba-4443-8121-0867169df831%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/2d7c0927-22ba-4443-8121-0867169df831%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEygQMpku8DGpOa%3DhFp7mS5E5TUaVNxjJwoG4RC0BM%3DfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: gitSCM failed after updates

[Mark Waite]

I'm glad that helped.  In the past, we've seen cases where a new version of
ssh surprises the credential integration that is used by the git plugin.  I
don't think your case is related to that, but I did see that Git for
Windows 2.22.0 now includes OpenSSH 8.0.  I need to add that version into
my test environment.  I'm not aware of any breakage with OpenSSH 8.0, but
we've been surprised in the past.

On Tue, Jun 11, 2019 at 3:09 PM Giles  wrote:

> Nailed it in one.
>
> I was sure it was a Jenkins issue ... but I'd upgraded Cygwin at the same
> time, and that probably included their version of git.  Which yes, is my
> default git.  I changed "Manage Jenkins" -> "Global Tool Configuration" ->
> git to the just-installed "Git for Windows", and ... fixed.  I may have to
> make some changes in the Jenkinsfiles themselves, but it seems clear now
> that the latest Cygwin git broke something, and that Git for Windows fixed
> it ...
>
> This was crisis-level breakage for my department - I can't thank you
> enough.
>
> On Tuesday, 11 June 2019 16:36:38 UTC-4, Mark Waite wrote:
>>
>> Are you quite sure that your configuration did not change in about the
>> same time as that upgrade?
>>
>> The log file indicates that you're running command line git as provided
>> by Cygwin.  Is that intentional?  Has it always been that way?
>>
>> I don't test the Jenkins git plugin with Cygwin.  I test with Git for
>> Windows.  I'm glad cygwin git works, but don't intend to apply effort to
>> make it work.
>>
>> I don't see anything suspicious or troubling in the list of updates.  As
>> far as I can tell, none of them should have changed that behavior of the
>> git plugin.
>>
>> On Tue, Jun 11, 2019 at 1:54 PM Giles  wrote:
>>
>>> I'm running Jenkins 2.164.3 on a Windows server.  It's been running well
>>> for several months.  Every Friday evening I do all the Jenkins plugin
>>> updates.  After this past Friday's updates (details below), all our jobs
>>> are broken - apparently because the GitSCM checkout is broken.  Our
>>> Jenkinsfiles are all stored in a git repo, so Jenkins attempts to pull a
>>> new version before running the job.  This now fails.  I created a test
>>> Jenkinsfile (editing directly in Jenkins rather than in the git repo) with
>>> this code in it:
>>>
>>> def scmVars = checkout(
>>> [
>>> $class: 'GitSCM',
>>> branches: [[name: '*/' + branch ]],
>>> doGenerateSubmoduleConfigurations: false,
>>> extensions: [],
>>> submoduleCfg: [],
>>> userRemoteConfigs: [
>>> [
>>> credentialsId: jenkinsCred,
>>> url: jenkinsRepo,
>>> ]
>>> ]
>>> ]
>>> );
>>>
>>> (Assume the "jenkinsCred" and "jenkinsRepo" values are correct.)  The
>>> failure looks like this:
>>>
>>> [Pipeline] {[Pipeline] checkoutusing credential 
>>> 29d83033-ebf6-4811-9c45-b0aadec775c2
>>>  > C:\cygwin64\bin\git.exe rev-parse --is-inside-work-tree # timeout=10
>>> Fetching changes from the remote Git repository
>>>  > C:\cygwin64\bin\git.exe config remote.origin.url g...@github.com:*/*.git 
>>> # timeout=10
>>> Fetching upstream changes from g...@github.com:*/*.git
>>>  > C:\cygwin64\bin\git.exe --version # timeout=10
>>> using GIT_SSH to set credentials Read-only access to the "Jenkins" 
>>> repository at github.com/*.
>>>  > C:\cygwin64\bin\git.exe fetch --tags --force --progress 
>>> g...@github.com:*/*.git +refs/heads/*:refs/remotes/origin/* # timeout=10
>>> ERROR: Error fetching remote repo 'origin'
>>> hudson.plugins.git.GitException: Failed to fetch from 
>>> g...@github.com:*/*.git
>>> at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:894)
>>> at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161)
>>> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)
>>> at 
>>> org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)
>>> at 
>>> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)
>>> at 
>>> org.jenkinsci.plugins.workflow.steps.scm.SC

Re: gitSCM failed after updates

[Mark Waite]

On Tue, Jun 11, 2019 at 4:53 PM Giles  wrote:

> Unfortunately, I appear to have gone from the frying pan to the fire.  I
> ran one deploy that hadn't worked previously and it did work, and I
> immediately responded with an "it's working" message.  And that single
> deploy still works.  But multiple others (all based on the same code, with
> only varying parameters) don't, all failing with this:
>
> Started by user Giles
> java.lang.NoSuchMethodError: 
> org.eclipse.jgit.lib.Repository.getRef(Ljava/lang/String;)Lorg/eclipse/jgit/lib/Ref;
>   at 
> jenkins.plugins.git.GitSCMFileSystem$1.invoke(GitSCMFileSystem.java:117)
>
> That may indicate that something has installed a newer version of JGit
than JGit 4.5 which is bundled with git client plugin 2.7.x.  JGit 4.5 and
prior versions provided the getRef(String) API.  Newer JGit versions (like
4.9, 5.1, 5.2, and 5.3) have deprecated or stopped delivering the
getRef(String) API.

Can you confirm that the git client plugin version you're running is 2.7.x
and not one of the pre-release 3.0 versions?  If it is not, then you likely
need to install the most recent 2.7 version.

Can you confirm that the git plugin version you're running is 3.9.x and not
one of the pre-release 4.0 versions?  I expect that is the case since
pre-release versions of git plugin 4.0.0 generally do not refer to
getRef(String).

That message is unrelated to the version of command line git installed on
the master.  That message is related to an internal mismatch between the
JGit API that is available in the running Jenkins process and the JGit API
that the git plugin requires.  The git plugin is expecting to find JGit 4.5
in the Jenkins process.  It does not seem to be there in this case.

This at least is a known error: it appears to happen when there's a newer
> version of git, or a misalignment of the git version and the git plugin.  I
> had initially installed the very new version of Git for Windows 2.22.0.  I
> downgraded that to 2.17.1.2, and eventually went to 2.21.0 - all resulting
> in the same failure.  Any thoughts?  It certainly doesn't seem to be the
> Git version, and the one working pipeline muddies the water further.
>
> On Tuesday, 11 June 2019 17:12:11 UTC-4, Mark Waite wrote:
>>
>> I'm glad that helped.  In the past, we've seen cases where a new version
>> of ssh surprises the credential integration that is used by the git
>> plugin.  I don't think your case is related to that, but I did see that Git
>> for Windows 2.22.0 now includes OpenSSH 8.0.  I need to add that version
>> into my test environment.  I'm not aware of any breakage with OpenSSH 8.0,
>> but we've been surprised in the past.
>>
>> On Tue, Jun 11, 2019 at 3:09 PM Giles  wrote:
>>
>>> Nailed it in one.
>>>
>>> I was sure it was a Jenkins issue ... but I'd upgraded Cygwin at the
>>> same time, and that probably included their version of git.  Which yes, is
>>> my default git.  I changed "Manage Jenkins" -> "Global Tool Configuration"
>>> -> git to the just-installed "Git for Windows", and ... fixed.  I may have
>>> to make some changes in the Jenkinsfiles themselves, but it seems clear now
>>> that the latest Cygwin git broke something, and that Git for Windows fixed
>>> it ...
>>>
>>> This was crisis-level breakage for my department - I can't thank you
>>> enough.
>>>
>>> On Tuesday, 11 June 2019 16:36:38 UTC-4, Mark Waite wrote:
>>>>
>>>> Are you quite sure that your configuration did not change in about the
>>>> same time as that upgrade?
>>>>
>>>> The log file indicates that you're running command line git as provided
>>>> by Cygwin.  Is that intentional?  Has it always been that way?
>>>>
>>>> I don't test the Jenkins git plugin with Cygwin.  I test with Git for
>>>> Windows.  I'm glad cygwin git works, but don't intend to apply effort to
>>>> make it work.
>>>>
>>>> I don't see anything suspicious or troubling in the list of updates.
>>>> As far as I can tell, none of them should have changed that behavior of the
>>>> git plugin.
>>>>
>>>> On Tue, Jun 11, 2019 at 1:54 PM Giles  wrote:
>>>>
>>>>> I'm running Jenkins 2.164.3 on a Windows server.  It's been running
>>>>> well for several months.  Every Friday evening I do all the Jenkins plugin
>>>>> updates.  After this past Friday's updates (details below), all our jobs
>>>>> are b

Re: gitSCM failed after updates

[Mark Waite]

On Wed, Jun 12, 2019 at 9:52 AM Giles  wrote:

> Hi Mark.
>
> Correct again:
>
> - Git plugin 3.10.0, now downgraded to 3.9.1
>

Git plugin 3.10.0 is a good choice.  Upgrade to it.


> - Git client plugin 3.0.0-rc, now downgraded to 2.7.6
>
>
Git client plugin 3.0.0-rc is a bad choice.  Don't upgrade (yet) to any git
client plugin newer than 2.7.x


> Deploys do now appear to all be working (this time I waited until we'd
> done a fair bit of testing before reporting ...).
>
> I upgraded the above plugins to 4.0.0-rc and 3.0.0-rc back in February
> because there were security advisories: I don't usually upgrade major
> versions immediately (especially not RC), instead waiting for them to have
> time to stabilize.
>
>
I think that you may have misread the security advisory.  No security
advisory has been issued that would require installation of a release
candidate.  Those two releases (git plugin 4.0.0-rc and git client plugin
3.0.0-rc) have been removed from the update center.  They have serious
compatibility problems which have been resolved in later pre-releases of
the plugins.


> These downgrades means that I'm now getting a fair bit of messaging from
> Jenkins about things I should upgrade or change:
>
> *Dependency errors:*
>
> Some plugins could not be loaded due to unsatisfied dependencies. Fix
> these issues and restart Jenkins to restore the functionality provided by
> these plugins.
> Git Parameter Plug-In version 0.9.10Jenkins Git plugin version
> 3.9.1 is older than required. To fix, install version 3.9.3 or later.
> GitHub Branch Source Plugin version 2.5.3Jenkins Git plugin version
> 3.9.1 is older than required. To fix, install version 3.9.3 or later.
>
> Warnings have been published for the following currently installed
> components.Git plugin 3.9.1
> <http://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin>CSRF
> vulnerability
> <https://jenkins.io/security/advisory/2019-01-28/#SECURITY-1095>
>
> Given that everything is working, I take it I should just ignore these for
> now?  Or possibly remove "Git Parameter Plug-In" and "GitHub Branch Source
> Plugin" as we apparently don't use them at all ...
>
> Once again, thank you very much for your help.
>
>
> On Tuesday, 11 June 2019 19:02:56 UTC-4, Mark Waite wrote:
>>
>>
>>
>> On Tue, Jun 11, 2019 at 4:53 PM Giles  wrote:
>>
>>> Unfortunately, I appear to have gone from the frying pan to the fire.  I
>>> ran one deploy that hadn't worked previously and it did work, and I
>>> immediately responded with an "it's working" message.  And that single
>>> deploy still works.  But multiple others (all based on the same code, with
>>> only varying parameters) don't, all failing with this:
>>>
>>> Started by user Giles
>>> java.lang.NoSuchMethodError: 
>>> org.eclipse.jgit.lib.Repository.getRef(Ljava/lang/String;)Lorg/eclipse/jgit/lib/Ref;
>>> at 
>>> jenkins.plugins.git.GitSCMFileSystem$1.invoke(GitSCMFileSystem.java:117)
>>>
>>> That may indicate that something has installed a newer version of JGit
>> than JGit 4.5 which is bundled with git client plugin 2.7.x.  JGit 4.5 and
>> prior versions provided the getRef(String) API.  Newer JGit versions (like
>> 4.9, 5.1, 5.2, and 5.3) have deprecated or stopped delivering the
>> getRef(String) API.
>>
>> Can you confirm that the git client plugin version you're running is
>> 2.7.x and not one of the pre-release 3.0 versions?  If it is not, then you
>> likely need to install the most recent 2.7 version.
>>
>> Can you confirm that the git plugin version you're running is 3.9.x and
>> not one of the pre-release 4.0 versions?  I expect that is the case since
>> pre-release versions of git plugin 4.0.0 generally do not refer to
>> getRef(String).
>>
>> That message is unrelated to the version of command line git installed on
>> the master.  That message is related to an internal mismatch between the
>> JGit API that is available in the running Jenkins process and the JGit API
>> that the git plugin requires.  The git plugin is expecting to find JGit 4.5
>> in the Jenkins process.  It does not seem to be there in this case.
>>
>> This at least is a known error: it appears to happen when there's a newer
>>> version of git, or a misalignment of the git version and the git plugin.  I
>>> had initially installed the very new version of Git for Windows 2.22.0.  I
>>> downgraded that to 2.17.1.2, and eventually went to 2.21.0 - all resulting
>>> in t

Re: TCP port for JNLP slave agents section not found in configure global security

[Mark Waite]

On Wed, Jun 12, 2019 at 11:22 PM Jim Barnebee  wrote:

>
>
> On Friday, May 24, 2019 at 6:10:40 AM UTC-6, Emilio Escobar Reyero wrote:
>>
>> Hi,
>>
>> I have started a 2.178 instance from scratch, installing suggested
>> plugins, and the agent port configuration is behind Markup Formatter as
>> expected.
>>
>>
>> [image: Screenshot 2019-05-24 at 13.36.39.png]
>>
>> On Fri, May 24, 2019 at 12:00 PM abhay srivastava 
>> wrote:
>>
>>> Hello all,
>>>
>>> Please help me on this issue.
>>> I am using jenkins 2.178 <https://jenkins.io/> version but section TCP
>>> port for JNLP slave agents section not found in configure global security
>>>
>>> [image: image.png]
>>>
>>> --
>>> Regards,
>>> Abhay Srivastava
>>> ---
>>> Mob-9160512000
>>>
>>> --
>>> 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 jenkins...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/CAPKgz8V0vk1RL1ujVYyQzVrK%3Dtr0RpkMpge5-WzvWQQOJJUAQw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAPKgz8V0vk1RL1ujVYyQzVrK%3Dtr0RpkMpge5-WzvWQQOJJUAQw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>>
>> Emilio Escobar
>> Software Engineer
>>
>> CloudBees, Inc.
>>
>> [image: CloudBees-Logo.png] <http://www.cloudbees.com>
>>
>>
>> E: eescoba...@cloudbees.com
>> Skype: escoem
>>
>
> So on your picture, it shows The TCP agent protocols- nothing about JNLP
> or JAVA - nor is this in the documentation anywhere. The documentation does
> not explain what port should be set or how to get JNLP working for a
> windows agent- they all just say use "JNLP" and "Java web start" which
> don't exist in 2.18.0 by default. There are lots of documentation pages
> that provide lots of different static port options for JNLP, none of which
> make the start agent with java web start option work in the agent
> configuration.. and this is after checking all the documentation for the
> java version 8, etc down in the details of the comments. It seems from the
> release notes that it was very visible and straightforward in 2.16 but was
> hidden? So how do you get to see JNLP protocols in that picture you posted?
>
>
Since you're trying to connect agents and the agents communicate over TCP,
use the section labeled "Agents" and the line that says "TCP port for
inbound agents".  Insert a valid port value for the TCP port for inbound
agents.  Apply that change.

Then add an agent and choose "Launch agent by connecting it to the master".

The phrasing has been improved significantly in the user interface by
removing the references to "JNLP".  The key difference between the agent
protocols is not the underlying transport, but rather which end initiates
the connection.  The agent launch method that was formerly called "JNLP" is
a launch method that initiates the agent connection from the agent to the
master.  The launch method called "ssh" initiates the connection from the
master to the agent.

[image:
screencapture-mark-pc2-markwaite-net-8080-computer-createItem-2019-06-12-23_33_38.png]


> *This message (including any attachments) is only for the use of the
> person(s) for whom it is intended. It may contain privileged, confidential
> or proprietary information. If you are not the intended recipient, you
> should not copy, distribute or use this information for any purpose, you
> should delete this message and inform the sender immediately. *
>
> --
> 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/d3653328-8c10-42fe-ac66-66a78dc309c0%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/d3653328-8c10-42fe-ac66-66a78dc309c0%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtGZo1xj1DudtF_1UjJ%3DWViU9SfUfGXLN99uk4q2%2B%3D5ACQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to add a windows slave into Jenkins 2.177

[Mark Waite]

The "Unsupported major/minor version" message means that you are attempting
to run Java code that requires a Java 8 virtual machine on a Java version
that is less than Java 8.  It could be a configuration error in your PATH.
It could be an installation error on the computer.  It could be that the
default Java installed on the computer is older than Java 8.

Refer to
https://stackoverflow.com/questions/22489398/unsupported-major-minor-version-52-0

On Mon, Jun 17, 2019 at 5:41 AM ANKUSH CHANDEL 
wrote:

> Hello All,
>
> Please help me out with adding a Windows slave into Jenkins.
> I am using Launch Method as "Launch agent by connecting it to the master".
>
> Which provides me three options to connect the slave machine.
>
> Connect agent to Jenkins one of these ways:
>
>-
>
>[image: launch agent]
>
> <https://phlox-dv.itn.intraorange:4443/computer/WIN_10_Ankush/slave-agent.jnlp>
>  Launch
>agent from browser
>-
>
>Run from agent command line:
>
>javaws http://Location:Port/computer/WIN_10_X/slave-agent.jnlp
>
>-
>
>Or if the agent is headless:
>
>java -jar agent.jar 
> <https://phlox-dv.itn.intraorange:4443/jnlpJars/agent.jar> -jnlpUrl 
> http://Location:Port/computer/WIN_10_X/slave-agent.jnlp -workDir 
> "C:\Jenkins\
>
>
> I have tired these steps but it saying unable to launch the application.
>
> C:\Jenkins>java -jar agent.jar -jnlpUrl 
> http://Location:Port/computer/WIN_10_X/slave-agent.jnlp
> -workDir "C:\Jenkins"
> Exception in thread "main" java.lang.UnsupportedClassVersionError:
> hudson/remoting/Launcher : Unsupported major.minor version 52.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(Unknown Source)
> at java.security.SecureClassLoader.defineClass(Unknown Source)
> at java.net.URLClassLoader.defineClass(Unknown Source)
> at java.net.URLClassLoader.access$100(Unknown Source)
> at java.net.URLClassLoader$1.run(Unknown Source)
> at java.net.URLClassLoader$1.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(Unknown Source)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at sun.launcher.LauncherHelper.checkAndLoadMain(Unknown Source)
>
> C:\Jenkins>javaws http://Location:Port
> /computer/WIN_10_X/slave-agent.jnlp
>
> C:\Jenkins>java -jar agent.jar -jnlpUrl 
> http://Location:Port/computer/WIN_10_X/slave-agent.jnlp
> -workDir "C:\Jenkins"
> Error: Registry key 'Software\JavaSoft\Java Runtime
> Environment'\CurrentVersion'
> has value '1.8', but '1.7' is required.
> Error: could not find java.dll
> Error: Could not find Java SE Runtime Environment.
>
>
> Please help me out with 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/35fd8d79-455b-4f35-8f27-ee5135b71893%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/35fd8d79-455b-4f35-8f27-ee5135b71893%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEGKoKeed47FezwLQsTWaRqqUsR1PKDqfSVqsiVy8zTZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: safe-shutdown does not wait for jobs to finish

[Mark Waite]

It is intentional that pipeline jobs do not prevent a shutdown of the
Jenkins server.  They are allowed to continue running on the agent hosting
them even while the Jenkins server restarts.  They are "durable" across
Jenkins server restarts.

When the Jenkins server restarts and the agent is reconnected, the status
of the job is communicated to the Jenkins server.

Refer to https://jenkins.io/doc/book/pipeline/scaling-pipeline/
<https://jenkins.io/doc/book/pipeline/scaling-pipeline/#what-am-i-giving-up-with-this-durability-setting-trade-off>
for
more details on pipeline durability settings and the compromises that you
may choose to make between pipeline durability and pipeline performance.

On Mon, Jun 24, 2019 at 6:45 AM Remo Meier  wrote:

> Hi
>
> We make use of:
>
> command: ["java", "-jar", "/var/jenkins_home/war/WEB-INF/jenkins-cli.jar", 
> "-s", "http://127.0.0.1:8080/scheduler";, "safe-shutdown"]
>
>
> To shutdown a Jenkins server. According to the documentation
> https://support.cloudbees.com/hc/en-us/articles/216118748-How-to-Start-Stop-or-Restart-your-Instance-
> and
> https://stackoverflow.com/questions/10238604/how-to-shutdown-my-jenkins-safely/13527164
> this should be fine to wait for job completion before shutdown. But the
> command for terminates the server immediately and restarts the Job after.
> Our job is a regular flow/pipeline definition:
>
> 
> 
> 
> 
> false
> 
> 
> 
> 
> 
> 0 3 * * *
> 
> 
> 
> 
> 
>  plugin="workflow-cps@2.55">
> 
> node {
> stage('Run') {
> sh '''
> #!/usr/bin/env bash
>
>
> exec kubectl run ...
>
> ...
> '''
> }
> }
> 
> true
> 
> 
> false
> 
>
>
> It shows log entries like:
>
> Ready to run at Mon Jun 24 11:46:22 GMT 2019
> Resuming build at Mon Jun 24 11:50:56 GMT 2019 after Jenkins restart
> Waiting to resume part of demo-import #71: Finished waiting
>
>
> In this case it runs some shell scripts. The documentation does not
> mention the use of termination signals or anything that would maybe stop
> the job?
>
> Thank you, Regards Remo
>
> --
> 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/c3fece50-f8b2-41e1-a2f3-9f5a7ce1bb38%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/c3fece50-f8b2-41e1-a2f3-9f5a7ce1bb38%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEbhi1drpiTSXKpSFicVJBeZ%2BPcoKVHV5Gj1efjnfpZYg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoClassDefFoundError: org/apache/sshd/common/KeyPairProvider on Fedora 30 fresh install of Jenkins

[Mark Waite]

I can't duplicate the problem you're reporting.  Unfortunately, lots of
information is missing from the report that might help others as they try
to help you.

I ran `docker run -t jenkins/jenkins:2.182` and confirmed there was no
failure in that execution.  Since you didn't describe the Jenkins version
you're using, I assumed the most recent weekly.  What Jenkins version
are you using?

I suspect there are many Jenkins users running various Jenkins versions on
Fedora 30.  What might be different about your installation compared to
those other users?  For example, are you using a different file system?
Did you install using the Jenkins RPM or are you running from a downloaded
copy of the war file?  Did you start the process from the command line or
are you running Jenkins as a daemon?

Did you start Jenkins with an empty JENKINS_HOME directory or were there
files or directories already in the JENKINS_HOME directory?  Are the file
and directory permissions correct in the JENKINS_HOME directory?

On Sat, Jun 29, 2019 at 5:13 AM Heymen Nicolaij 
wrote:

> There seem to several class path errors as if the lib folder of the web
> app can't be found since the required classes can be found there as far as
> I can see.
>
> Op zaterdag 29 juni 2019 13:01:55 UTC+2 schreef Heymen Nicolaij:
>>
>> Hi,
>>
>> Following stacktrace appears on fresh install of Jenkins on Fedora 30
>> machine:
>>
>> java.lang.NoClassDefFoundError: org/apache/sshd/common/KeyPairProvider
>> at java.base/java.lang.Class.getDeclaredMethods0(Native Method)
>> at
>> java.base/java.lang.Class.privateGetDeclaredMethods(Class.java:3167)
>> at java.base/java.lang.Class.getDeclaredMethods(Class.java:2310)
>> at
>> org.jvnet.hudson.annotation_indexer.Index$2$1.fetch(Index.java:103)
>> at
>> org.jvnet.hudson.annotation_indexer.Index$2$1.hasNext(Index.java:73)
>> at
>> org.jvnet.hudson.annotation_indexer.SubtypeIterator.fetch(SubtypeIterator.java:18)
>> at
>> org.jvnet.hudson.annotation_indexer.SubtypeIterator.hasNext(SubtypeIterator.java:28)
>> at
>> hudson.init.TaskMethodFinder.discoverTasks(TaskMethodFinder.java:56)
>> at
>> hudson.init.InitializerFinder.discoverTasks(InitializerFinder.java:33)
>> at
>> hudson.init.TaskMethodFinder.discoverTasks(TaskMethodFinder.java:32)
>> at
>> org.jvnet.hudson.reactor.TaskBuilder$2.discoverTasks(TaskBuilder.java:63)
>> at org.jvnet.hudson.reactor.Reactor.(Reactor.java:151)
>> at org.jvnet.hudson.reactor.Reactor.(Reactor.java:156)
>> at jenkins.model.Jenkins$8.(Jenkins.java:909)
>> at jenkins.model.Jenkins.executeReactor(Jenkins.java:909)
>> at jenkins.model.Jenkins.(Jenkins.java:818)
>> at hudson.model.Hudson.(Hudson.java:83)
>> at hudson.model.Hudson.(Hudson.java:79)
>> at hudson.WebAppMain$3.run(WebAppMain.java:225)
>> Caused by: java.lang.ClassNotFoundException:
>> org.apache.sshd.common.KeyPairProvider
>> at java.base/java.net
>> .URLClassLoader.findClass(URLClassLoader.java:471)
>> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
>> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
>> at
>> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:430)
>> at
>> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:383)
>> ... 19 more
>>
>> Any ideas ?
>>
>> Full logging can be found attached.
>>
>> Kind regards, Heymen
>>
>> --
> 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/ff09aad6-b461-4fab-8bea-bd680648d3b7%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/ff09aad6-b461-4fab-8bea-bd680648d3b7%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHuWrM9Sa-Da3kL8XYo8axMU%2BcGyBcbAhZB-RPQ4iN7cQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoClassDefFoundError: org/apache/sshd/common/KeyPairProvider on Fedora 30 fresh install of Jenkins

[Mark Waite]

.1.jar:/usr/share/java/jetty8/jetty-xml-8.1.jar:/usr/share/java/jetty8/jetty-continuation-8.1.jar:/usr/share/java/jetty8/jetty-io-8.1.jar:/usr/share/java/jetty8/jetty-http-8.1.jar:/usr/share/java/jetty8/jetty-servlet-8.1.jar:/usr/share/java/jetty8/jetty-util-8.1.jar:/usr/share/java/jetty8/jetty-security-8.1.jar:/usr/share/java/jetty8/jetty-webapp-8.1.jar:/usr/share/java/jetty8/jetty-server-8.1.jar:/usr/share/java/jetty8/jetty-xml-8.1.jar:/usr/share/java/jetty8/jetty-continuation-8.1.jar:/usr/share/java/jetty8/jetty-io-8.1.jar:/usr/share/java/jetty8/jetty-http-8.1.jar:/usr/share/java/jetty8/jetty-servlet-8.1.jar:/usr/share/java/jetty8/jetty-util-8.1.jar:/usr/share/java/jetty8/jetty-security-8.1.jar:/usr/share/java/jetty8/jetty-webapp-8.1.jar:/usr/share/java/jetty8/jetty-server-8.1.jar:/usr/share/java/jetty8/jetty-xml-8.1.jar:/usr/share/java/jetty8/jetty-continuation-8.1.jar:/usr/share/java/jetty8/jetty-io-8.1.jar:/usr/share/java/jetty8/jetty-http-8.1.jar:/usr/share/java/jetty8/jetty-servlet-8.1.jar:/usr/share/java/jetty8/jetty-util-8.1.jar:/usr/share/java/jetty8/jetty-security-8.1.jar:/usr/share/java/jetty8/jetty-webapp-8.1.jar:/usr/share/java/jetty8/jetty-server-8.1.jar:/usr/share/java/jetty8/jetty-xml-8.1.jar:/usr/share/java/jetty8/jetty-continuation-8.1.jar:/usr/share/java/jetty8/jetty-io-8.1.jar:/usr/share/java/jetty8/jetty-http-8.1.jar:/usr/share/java/glassfish-servlet-api.jar
> Main --logfile=/var/log/jenkins/jenkins.log
> --extractedFilesFolder=/usr/share/jenkins/webroot/
> --webroot=/usr/share/jenkins/webroot/ --daemon --httpPort=9090
> --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20
>
>
> Op zaterdag 29 juni 2019 13:01:55 UTC+2 schreef Heymen Nicolaij:
>>
>> Hi,
>>
>> Following stacktrace appears on fresh install of Jenkins on Fedora 30
>> machine:
>>
>> java.lang.NoClassDefFoundError: org/apache/sshd/common/KeyPairProvider
>> at java.base/java.lang.Class.getDeclaredMethods0(Native Method)
>> at
>> java.base/java.lang.Class.privateGetDeclaredMethods(Class.java:3167)
>> at java.base/java.lang.Class.getDeclaredMethods(Class.java:2310)
>> at
>> org.jvnet.hudson.annotation_indexer.Index$2$1.fetch(Index.java:103)
>> at
>> org.jvnet.hudson.annotation_indexer.Index$2$1.hasNext(Index.java:73)
>> at
>> org.jvnet.hudson.annotation_indexer.SubtypeIterator.fetch(SubtypeIterator.java:18)
>> at
>> org.jvnet.hudson.annotation_indexer.SubtypeIterator.hasNext(SubtypeIterator.java:28)
>> at
>> hudson.init.TaskMethodFinder.discoverTasks(TaskMethodFinder.java:56)
>> at
>> hudson.init.InitializerFinder.discoverTasks(InitializerFinder.java:33)
>> at
>> hudson.init.TaskMethodFinder.discoverTasks(TaskMethodFinder.java:32)
>> at
>> org.jvnet.hudson.reactor.TaskBuilder$2.discoverTasks(TaskBuilder.java:63)
>> at org.jvnet.hudson.reactor.Reactor.(Reactor.java:151)
>> at org.jvnet.hudson.reactor.Reactor.(Reactor.java:156)
>> at jenkins.model.Jenkins$8.(Jenkins.java:909)
>> at jenkins.model.Jenkins.executeReactor(Jenkins.java:909)
>> at jenkins.model.Jenkins.(Jenkins.java:818)
>> at hudson.model.Hudson.(Hudson.java:83)
>> at hudson.model.Hudson.(Hudson.java:79)
>> at hudson.WebAppMain$3.run(WebAppMain.java:225)
>> Caused by: java.lang.ClassNotFoundException:
>> org.apache.sshd.common.KeyPairProvider
>> at java.base/java.net
>> .URLClassLoader.findClass(URLClassLoader.java:471)
>> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
>> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
>> at
>> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:430)
>> at
>> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:383)
>> ... 19 more
>>
>> Any ideas ?
>>
>> Full logging can be found attached.
>>
>> Kind regards, Heymen
>>
>> --
> 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/9f4dd97e-5e87-43b0-b590-32b70eafa31c%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/9f4dd97e-5e87-43b0-b590-32b70eafa31c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEeEssZWGfs-Gvy7ww7tHZ1kjBO%3DWRrkmBV6zq%2B0U%3DE2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoClassDefFoundError: org/apache/sshd/common/KeyPairProvider on Fedora 30 fresh install of Jenkins

[Mark Waite]

If that is not sufficient to resolve the issue, you might also try the
following steps to confirm that your system is configured so that it can
run Jenkins.  Some of the steps you might check include:

Check that you are running either Java 8 or Java 11.  Other Java versions
are not supported.

$ java -version

Download the latest Jenkins long term support release and run it from the
war file to confirm that it runs and you can connect to it.  You don't want
to run it long term like that, just confirm that it works before installing
the operating system package.

$ wget http://mirrors.jenkins.io/war-stable/latest/jenkins.war && java -jar
jenkins.war



On Sat, Jun 29, 2019 at 10:38 AM Mark Waite 
wrote:

> That listing seems to indicate that if you attempt to install Jenkins from
> your current repository definition, it will install Jenkins 1.651.3.
> Jenkins 1.651.3 is very old.
>
> The Jenkins installation instructions for Fedora are available in the
> Jenkins User Handbook section on "Installing" at
> https://jenkins.io/doc/book/installing/#fedora .  Those instructions add
> https://jenkins.io/doc/book/installing/#fedora as a repository and they
> have you install with `dnf`.
>
> There are also instructions for CentOS and Red Hat at
> http://pkg.jenkins-ci.org/redhat/ .  They are not part of the Jenkins
> User Handbook, but I believe they are known to work for CentOS
> distributions.
>
> On Sat, Jun 29, 2019 at 6:32 AM Heymen Nicolaij 
> wrote:
>
>> Extra info I installed from RPM weekly:
>>
>> rpm -q -a|grep jenkins
>> jenkins-webapp-1.651.3-10.fc30.noarch
>> jenkins-credentials-plugin-1.27-1.fc25.noarch
>> trilead-ssh2-217-12.jenkins8.fc30.noarch
>> jenkins-cli-1.651.3-10.fc30.noarch
>> jenkins-core-1.651.3-10.fc30.noarch
>> js-yui2-jenkins-2.9.0-10.fc24.noarch
>> jenkins-remoting-webapp-2.62.3-1.fc26.noarch
>> jenkins-pam-auth-plugin-1.2-3.fc24.noarch
>> jenkins-instance-identity-1.4-5.fc24.noarch
>> jenkins-script-security-plugin-1.18.1-1.fc25.noarch
>> jenkins-commons-jelly-1.1.20120928-10.fc24.noarch
>> jenkins-extras-memory-monitor-1.9-3.fc24.noarch
>> jenkins-external-monitor-job-plugin-1.4-4.fc24.noarch
>> jenkins-matrix-project-plugin-1.6-2.fc24.noarch
>> jenkins-javadoc-plugin-1.3-4.fc24.noarch
>> jenkins-matrix-auth-plugin-1.2-3.fc24.noarch
>> jenkins-icon-shim-1.0.4-4.fc24.noarch
>> jenkins-ssh-cli-auth-1.2-8.fc24.noarch
>> jenkins-version-number-1.1-11.fc30.noarch
>> jenkins-mailer-plugin-1.17-1.fc25.noarch
>> jenkins-winstone-2.8-10.fc30.noarch
>> jenkins-crypto-util-1.4-6.fc24.noarch
>> jenkins-ssh-slaves-plugin-1.10-3.fc24.noarch
>> jenkins-ldap-plugin-1.11-3.fc24.noarch
>> jenkins-1.651.3-10.fc30.noarch
>> jenkins-executable-war-webroot-1.29-11.fc30.noarch
>> jenkins-remoting-2.62.3-1.fc26.noarch
>> jenkins-task-reactor-1.4-9.fc30.noarch
>> jenkins-jexl-1.1-5.20111212.fc24.noarch
>> jenkins-junit-plugin-1.12-1.fc25.noarch
>> jenkins-json-lib-2.4-16.fc30.noarch
>> jenkins-ant-plugin-1.2-6.fc24.noarch
>> jenkins-antisamy-markup-formatter-plugin-1.3-2.fc24.noarch
>> jenkins-ssh-credentials-plugin-1.11-4.fc24.noarch
>> jenkins-xstream-1.4.7-15.jenkins1.fc30.noarch
>>
>> And see the following command running:
>>
>> ps -ef|grep java
>> jenkins  23630 1  3 14:25 ?00:00:15 /etc/alternatives/java
>> -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true
>> -DJENKINS_HOME=/var/lib/jenkins -cp
>> /usr/share/jenkins/webroot//:/usr/share/jenkins/webroot//winstone.jar:/usr/share/java/jetty8/jetty-servlet-8.1.jar:/usr/share/java/jetty8/jetty-util-8.1.jar:/usr/share/java/jetty8/jetty-security-8.1.jar:/usr/share/java/jetty8/jetty-webapp-8.1.jar:/usr/share/java/jetty8/jetty-server-8.1.jar:/usr/share/java/jetty8/jetty-xml-8.1.jar:/usr/share/java/jetty8/jetty-continuation-8.1.jar:/usr/share/java/jetty8/jetty-io-8.1.jar:/usr/share/java/jetty8/jetty-http-8.1.jar:/usr/share/java/jetty8/jetty-servlet-8.1.jar:/usr/share/java/jetty8/jetty-util-8.1.jar:/usr/share/java/jetty8/jetty-security-8.1.jar:/usr/share/java/jetty8/jetty-webapp-8.1.jar:/usr/share/java/jetty8/jetty-server-8.1.jar:/usr/share/java/jetty8/jetty-xml-8.1.jar:/usr/share/java/jetty8/jetty-continuation-8.1.jar:/usr/share/java/jetty8/jetty-io-8.1.jar:/usr/share/java/jetty8/jetty-http-8.1.jar:/usr/share/java/jetty8/jetty-servlet-8.1.jar:/usr/share/java/jetty8/jetty-util-8.1.jar:/usr/share/java/jetty8/jetty-security-8.1.jar:/usr/share/java/jetty8/jetty-webapp-8.1.jar:/usr/share/java/jetty8/jetty-server-8.1.jar:/usr/share/java/jetty8/jetty-xml-8.1.jar:/usr/share/java/jetty8/jetty-continuation-8.1.jar:/usr/share/java/jetty8/jetty-io-8.1.jar:/usr/share/java/jetty8/jetty-http-8.1.jar:/usr/shar

Re: fatal: git index-pack failed

[Mark Waite]

:  72% (83/114)
> remote: Compressing objects:  73% (84/114)
> remote: Compressing objects:  74% (85/114)
> remote: Compressing objects:  75% (86/114)
> remote: Compressing objects:  76% (87/114)
> remote: Compressing objects:  77% (88/114)
> remote: Compressing objects:  78% (89/114)
> remote: Compressing objects:  79% (91/114)
> remote: Compressing objects:  80% (92/114)
> remote: Compressing objects:  81% (93/114)
> remote: Compressing objects:  82% (94/114)
> remote: Compressing objects:  83% (95/114)
> remote: Compressing objects:  84% (96/114)
> remote: Compressing objects:  85% (97/114)
> remote: Compressing objects:  86% (99/114)
> remote: Compressing objects:  87% (100/114)
> remote: Compressing objects:  88% (101/114)
> remote: Compressing objects:  89% (102/114)
> remote: Compressing objects:  90% (103/114)
> remote: Compressing objects:  91% (104/114)
> remote: Compressing objects:  92% (105/114)
> remote: Compressing objects:  93% (107/114)
> remote: Compressing objects:  94% (108/114)
> remote: Compressing objects:  95% (109/114)
> remote: Compressing objects:  96% (110/114)
> remote: Compressing objects:  97% (111/114)
> remote: Compressing objects:  98% (112/114)
> remote: Compressing objects:  99% (113/114)
> remote: Compressing objects: 100% (114/114)
> remote: Compressing objects: 100% (114/114), done.
> Receiving objects:   0% (1/114)
> Receiving objects:   1% (2/114)
> Receiving objects:   2% (3/114)
> Receiving objects:   3% (4/114)
> Receiving objects:   4% (5/114)
> Receiving objects:   5% (6/114)
> Receiving objects:   6% (7/114)
> Receiving objects:   7% (8/114)
> Receiving objects:   8% (10/114)
> Receiving objects:   9% (11/114)
> Receiving objects:  10% (12/114)
> Receiving objects:  11% (13/114)
> Receiving objects:  12% (14/114)
> Receiving objects:  13% (15/114)
> Receiving objects:  14% (16/114)
> error: object file .git/objects/21/a28795e9c6fa55f026860e0c2f0b08d1b31611
> is empty
> fatal: cannot read existing object info
> 21a28795e9c6fa55f026860e0c2f0b08d1b31611
> fatal: index-pack failed
>
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442)
> at
> jenkins.plugins.git.AbstractGitSCMSource$8.run(AbstractGitSCMSource.java:575)
> at
> jenkins.plugins.git.AbstractGitSCMSource$8.run(AbstractGitSCMSource.java:556)
> at
> jenkins.plugins.git.AbstractGitSCMSource.doRetrieve(AbstractGitSCMSource.java:367)
> at
> jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:556)
> at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373)
> at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283)
> at
> jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634)
> at
> com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277)
> at
> com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164)
> at
> jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1025)
> at hudson.model.ResourceController.execute(ResourceController.java:97)
> at hudson.model.Executor.run(Executor.java:429)
> Finished: FAILURE
>
> --
> 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/b6a89f4c-7b2e-441d-ba26-cf46a762b0af%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/b6a89f4c-7b2e-441d-ba26-cf46a762b0af%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtH0ivhBiPTaWa0B1BeT_9sYaXiNKzDcJShLU_%3DvWP%3DNWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: fatal: git index-pack failed

[Mark Waite]

Sorry, I didn't read your description thoroughly enough.  You said:

I'm getting a fatal error reported when doing a repository scan (Scan
> Multibranch Pipeline Now) which was previously working.
>

The command line git log output indicates that your repository is large
enough that it may be reaching the default 10 minute clone timeout.  Refer
to https://issues.jenkins-ci.org/browse/JENKINS-38973 for a discussion of
possible workarounds.

On Tue, Jul 2, 2019 at 6:31 AM Mark Waite  wrote:

> The repository in the workspace on the agent running that build is
> probably damaged.  Wipe the workspace on the agent and run the job again.
>
> If wiping the workspace and running the job again does not resolve it, you
> may also be encountering a timeout while cloning the repository.  Increase
> the timeout for the repository clone from its default of 10 minutes to
> something large enough that it will allow you to clone the repository.
>
> The amount of output you're showing hints that the repository is large or
> the network connection between the agent and the upstream cloned repository
> is slow.  In either of those cases, you probably want to reduce the clone
> time and the disc space use by applying one or more of the techniques
> described in "Git in the Large <https://youtu.be/jBGFjFc6Jf8?t=6434>".
> Those techniques include (1) reference repositories on the agent, (2)
> narrow refspecs, (3) shallow clones, and (4) sparse checkouts.
>
> If this is a Pipeline repository and the failure is during the initial
> clone of the repository, then you may also need to use lightweight checkout
> to only checkout the Jenkinsfile rather than the entire repository.
> Alternately for Pipelines, if your git provider is GitHub, Bitbucket, or
> Gitea, you can significantly improve performance by using those branch
> source plugins to manage the Pipeline instead of relying on low-level
> command line git calls.
>
> Reference repositories are usually the most effective technique to reduce
> data transfer time and disc space use for large git repositories.  Allan
> Burdajewicz of CloudBees wrote a great article on reference repositories at
> https://support.cloudbees.com/hc/en-us/articles/115001728812-Using-a-Git-reference-repository
>  .
>
> On Tue, Jul 2, 2019 at 5:51 AM Kevin Stevens  wrote:
>
>> I'm getting a fatal error reported when doing a repository scan (Scan
>> Multibranch Pipeline Now) which was previously working.
>> I've run the git commands manually from the command line (copied and
>> pasted) and they appear to work correctly, so it seems like a problem with
>> the Jenkins git client plugin.
>>
>> The scan log is below (repository name and account information modified
>> for security reasons).
>> I'm not clear if this is a GIT or a Jenkins git client problem. I've
>> cleared the Jenkins workspace and updated to the latest Jenkins plugins
>> (running on Ubuntu 18.04).
>> Is anyone able to offer help in debugging this issue please?
>>
>>
>> [Tue Jul 02 09:48:00 BST 2019] Starting branch indexing...
>>  > git --version # timeout=10
>> using GIT_ASKPASS to set credentials Jenkins Bitbucket User
>>  > git ls-remote --symref 
>> g...@bitbucket.org:my-company-name/my-repository-name.git
>> # timeout=10
>>  > git rev-parse --is-inside-work-tree # timeout=10
>> Setting origin to g...@bitbucket.org:
>> my-company-name/my-repository-name.git
>>  > git config remote.origin.url 
>> g...@bitbucket.org:my-company-name/my-repository-name.git
>> # timeout=10
>> Fetching & pruning origin...
>> Listing remote references...
>>  > git config --get remote.origin.url # timeout=10
>>  > git --version # timeout=10
>> using GIT_ASKPASS to set credentials Jenkins Bitbucket User
>>  > git ls-remote -h g...@bitbucket.org:my-company-name/my-repository-name.git
>> # timeout=10
>> Fetching upstream changes from origin
>>  > git config --get remote.origin.url # timeout=10
>> using GIT_ASKPASS to set credentials Jenkins Bitbucket User
>>  > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
>> --prune
>> ERROR: [Tue Jul 02 09:48:10 BST 2019] Could not fetch branches from
>> source 498872a6-3888-419f-9d2f-a2baa4520968
>> hudson.plugins.git.GitException: Command "git fetch --tags --progress
>> origin +refs/heads/*:refs/remotes/origin/* --prune" returned status code
>> 128:
>> stdout:
>> stderr: remote: Counting objects: 114, done.
>> remote: Compressing objects:   0% (1/114)
>> remote: Compressing objects:   1% (2/114)
>> remote: Compressing obje

Re: fatal: git index-pack failed

[Mark Waite]

That's great news.  A git repository that needs more than 10 minutes to
clone is a really good candidate for reference repositories and all the
other techniques suggested in the "Git in the Large" video.  The first
preference with repositories that large is to reduce their size by removing
large files from the repository.  Unfortunately, most organizations can't
do that.  A previous organization where I worked had a 25 GB repository
that just kept growing due to large binary checkins.  Git large file
storage (LFS) is another lifesaver to avoid creating large repositories.
Good luck!

On Tue, Jul 2, 2019 at 8:49 AM Kevin Stevens  wrote:

> Hi Mark - whilst looking for a place to stash my reference repo I
> discovered that Jenkins is keeping a cache of git checkouts in the
> /var/lib/jenkins/cache folder, and by deleting these files the multibranch
> pipeline scan now succeeds, so there was obviously something corrupt in
> that cache (possibly caused by a recent instability issue with the Jenkins
> server hardware), so I've not implemented a reference repo.
> Thanks for your help ;-)
>
> Kevin
>
> On Tuesday, 2 July 2019 15:25:41 UTC+1, Kevin Stevens wrote:
>>
>> Thanks for the responses and the issue link Mark, I've increased the Git
>> timeout value as described, and confirmed in the log that the 30 minute
>> timeout is in effect, but I'm still seeing the same failure (i.e. fatal
>> error in Scan Multibranch Pipeline Now).
>> I was pretty confident that there's not a timeout issue as the failure
>> occurs in a matter of seconds, so I'm going to try the reference repo
>> approach which seems like it should work, but it would appear to be an
>> issue within the git client parsing to me. I'll confirm my outcome.
>>
>> Regards, Kevin
>>
>> On Tuesday, 2 July 2019 13:37:41 UTC+1, Mark Waite wrote:
>>>
>>> Sorry, I didn't read your description thoroughly enough.  You said:
>>>
>>> I'm getting a fatal error reported when doing a repository scan (Scan
>>>> Multibranch Pipeline Now) which was previously working.
>>>>
>>>
>>> The command line git log output indicates that your repository is large
>>> enough that it may be reaching the default 10 minute clone timeout.  Refer
>>> to https://issues.jenkins-ci.org/browse/JENKINS-38973 for a discussion
>>> of possible workarounds.
>>>
>>> On Tue, Jul 2, 2019 at 6:31 AM Mark Waite  wrote:
>>>
>>>> The repository in the workspace on the agent running that build is
>>>> probably damaged.  Wipe the workspace on the agent and run the job again.
>>>>
>>>> If wiping the workspace and running the job again does not resolve it,
>>>> you may also be encountering a timeout while cloning the repository.
>>>> Increase the timeout for the repository clone from its default of 10
>>>> minutes to something large enough that it will allow you to clone the
>>>> repository.
>>>>
>>>> The amount of output you're showing hints that the repository is large
>>>> or the network connection between the agent and the upstream cloned
>>>> repository is slow.  In either of those cases, you probably want to reduce
>>>> the clone time and the disc space use by applying one or more of the
>>>> techniques described in "Git in the Large
>>>> <https://youtu.be/jBGFjFc6Jf8?t=6434>".  Those techniques include (1)
>>>> reference repositories on the agent, (2) narrow refspecs, (3) shallow
>>>> clones, and (4) sparse checkouts.
>>>>
>>>> If this is a Pipeline repository and the failure is during the initial
>>>> clone of the repository, then you may also need to use lightweight checkout
>>>> to only checkout the Jenkinsfile rather than the entire repository.
>>>> Alternately for Pipelines, if your git provider is GitHub, Bitbucket, or
>>>> Gitea, you can significantly improve performance by using those branch
>>>> source plugins to manage the Pipeline instead of relying on low-level
>>>> command line git calls.
>>>>
>>>> Reference repositories are usually the most effective technique to
>>>> reduce data transfer time and disc space use for large git repositories.
>>>> Allan Burdajewicz of CloudBees wrote a great article on reference
>>>> repositories at
>>>> https://support.cloudbees.com/hc/en-us/articles/115001728812-Using-a-Git-reference-repository
>>>>  .
>>>>
>>>> On Tue, Jul 2, 2019 a

Re: Skip a Jenkins job build in a pipeline

[Mark Waite]

One technique is to create a single Jenkins Pipeline job that performs all
10 of those steps, then use the declarative Pipeline ability to
conditionally skip a step based on conditions you decide.

However, I've never tried to manage that complex a Pipeline job, so I can't
comment more than to suggest you might experiment with that technique.

On Tue, Jul 2, 2019 at 7:48 AM Vijay Gongle  wrote:

> I have a Jenkins pipeline which has 10 Jobs configured to run one after
> the other in the post build action.
> Anytime there's a change in Job's related git code, the build is triggered
> and all the following jobs run though rest of the Job code were not
> committed.
>
> For e.g, in a series of 10 jobs in the pipeline, if there's a code change
> in 2nd job but not in 3rd job then I would like to skip the 2nd job and
> build the 3rd job directly.
> Likewise, any job where the code is not changed, would like to skip and
> jump to following job.
>
> Please help me if there;s a way to resolve this unwanted builds in the
> pipeline.
>
> --
> 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/345f6008-fdd7-4ff8-bb84-4018c99dd956%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/345f6008-fdd7-4ff8-bb84-4018c99dd956%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHcL8LwBDhhT9v9Sg077f%2Bq9%2BSevKzuQb8vZM%3DMcYnVWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Git Plugin - Too Verbose

[Mark Waite]

Unfortunately, there isn't currently a way to quiet the log file noise from
the git plugin.

On Fri, Jul 5, 2019 at 1:21 PM Shaun McArthur  wrote:

> Is there a way to impose something like --quiet on the Git Plugin?
>
> It's way too verbose and the console gets cluttered.
>
> Thanks,
> Shaun
>
> --
> 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/d83dd1a1-d2f0-4dfd-9db0-a435c4cbb6f7%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/d83dd1a1-d2f0-4dfd-9db0-a435c4cbb6f7%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHK196N6CY4pgnASHAd9ctkzOO3Pt0_M%2BH8WASCUEZwKQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Github Branch Source Plugin not allowing individual folder configuration

[Mark Waite]

I believe that it once was possible to modify the individual job
definitions of a GitHub Branch Source folder.  However, I believe the
modifications were also periodically reset (possibly by scanning for new
changes or by detecting new branches).  I believe that the capability to
edit individual job definitions was intentionally removed.

At least that has been my assumption.

On Mon, Jul 8, 2019 at 1:29 PM Yash Nalla  wrote:

> Hi all,
>
> The subject line kinda says it all. The documentation for Github Branch
> Source plugin: https://go.cloudbees.com/docs/plugins/github-branch-source/ 
> says
> that users can go in and "configuring different settings on each of those
> folders[repositories] if needed." However when i navigate into any of these
> folders/or use the drop down I can only View Configuration rather than edit
> it. I believe this might be some sort of bug because many of the fields in
> the view configuration are editable and would make sense to be editable.
>
> Best,
>
> Yash nalla
>
> --
> 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/6b0971fa-c016-4822-a4a2-15cf239d6392%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/6b0971fa-c016-4822-a4a2-15cf239d6392%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHe6iVi3JU9JER%3D1%2Bvm4mUwjhmgxvTtLnZ9LetzDiN2uQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Github Branch Source Plugin not allowing individual folder configuration

[Mark Waite]

I may also be completely wrong.  My recollection is only a poor memory, not
anything that I verified by checking the behavior of past releases.  As far
as I can tell, it is intentional that the jobs created by the GitHub Branch
Source plugin cannot be reconfigured.

On Mon, Jul 8, 2019 at 2:01 PM Yash Nalla  wrote:

> I just went through the changelogs of the plugin and nothing like that is
> mentioned? Though if all the edits to job definitions were already being
> rolled back periodically I guess just removing that ability doesn't change
> anything in the long term.
>
> On Monday, July 8, 2019 at 3:32:18 PM UTC-4, Mark Waite wrote:
>>
>> I believe that it once was possible to modify the individual job
>> definitions of a GitHub Branch Source folder.  However, I believe the
>> modifications were also periodically reset (possibly by scanning for new
>> changes or by detecting new branches).  I believe that the capability to
>> edit individual job definitions was intentionally removed.
>>
>> At least that has been my assumption.
>>
>> On Mon, Jul 8, 2019 at 1:29 PM Yash Nalla  wrote:
>>
>>> Hi all,
>>>
>>> The subject line kinda says it all. The documentation for Github Branch
>>> Source plugin:
>>> https://go.cloudbees.com/docs/plugins/github-branch-source/ says that
>>> users can go in and "configuring different settings on each of those
>>> folders[repositories] if needed." However when i navigate into any of these
>>> folders/or use the drop down I can only View Configuration rather than edit
>>> it. I believe this might be some sort of bug because many of the fields in
>>> the view configuration are editable and would make sense to be editable.
>>>
>>> Best,
>>>
>>> Yash nalla
>>>
>>> --
>>> 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 jenkins...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/6b0971fa-c016-4822-a4a2-15cf239d6392%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/6b0971fa-c016-4822-a4a2-15cf239d6392%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> 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/08a6e802-48ae-40d9-9e51-c4da190c40f2%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/08a6e802-48ae-40d9-9e51-c4da190c40f2%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtFdUEsyjUr0j3qr39d5M%2B9dpZb5MPu2kDobRXcjx5APww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Github Branch Source Plugin not allowing individual folder configuration

[Mark Waite]

Wouldn't it be best to make the necessary changes inside the build scripts
that are called from the Jenkinsfile?

On Mon, Jul 8, 2019 at 2:15 PM Yash Nalla  wrote:

> If my use case requires me to make changes to individual job definitions
> EX: the build path, does anyone have any suggestions on how to do so within
> a GitHub organization?
>
>>
> Best,
>
> Yash Nalla
>
> --
> 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/9c307d05-ea7e-4805-a782-c0f163bd29f6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/9c307d05-ea7e-4805-a782-c0f163bd29f6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtEfeig%3DgkrE77LSZw%3DbLyaDu%3D3thK10L8o9-sPRA9EF1w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Running jobs sequentially on Jenkins ?

[Mark Waite]

https://jenkins.io/doc/book/pipeline/  is the online documentation for
Jenkins Pipeline.

There are also several Jenkins Minute video tutorials
<https://www.youtube.com/watch?v=FhDomw6BaHU&list=PLvBBnHmZuNQJsTCaXs91HRrmso7RNSl-L>
available
from YouTube

   - Creating your first Pipeline in Blue Ocean -
   https://www.youtube.com/watch?v=FhDomw6BaHU
   - Recording test results and artifacts -
   https://www.youtube.com/watch?v=c9E8kGuAwLU
   
<https://www.youtube.com/watch?v=c9E8kGuAwLU&list=PLvBBnHmZuNQJsTCaXs91HRrmso7RNSl-L&index=4>
   - Parallel stages -  https://www.youtube.com/watch?v=cCSZx3HmCwY
   
<https://www.youtube.com/watch?v=cCSZx3HmCwY&list=PLvBBnHmZuNQJsTCaXs91HRrmso7RNSl-L&index=7>
   - Conditional stages -  https://www.youtube.com/watch?v=YWb5Is6VwPg
   
<https://www.youtube.com/watch?v=YWb5Is6VwPg&list=PLvBBnHmZuNQJsTCaXs91HRrmso7RNSl-L&index=8>
   - Using git environment variables -
   https://www.youtube.com/watch?v=tziVDpNYlgM
   
<https://www.youtube.com/watch?v=tziVDpNYlgM&list=PLvBBnHmZuNQJsTCaXs91HRrmso7RNSl-L&index=9>

CloudBees also offers a free self-paced course, "Pipeline Fundamentals" at
https://standard.cbu.cloudbees.com/cloudbees-university-jenkins-pipeline-fundamentals

There is also a 24 minute video on creating a Pipeline with Blue Ocean at
https://www.youtube.com/watch?v=LzFmTiH8nos


On Tue, Jul 9, 2019 at 6:35 AM srinivasa rao 
wrote:

> Request to everyone please share Jenkins pipeline flow document
>
> --
> 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/0cb1d349-16bf-4039-8973-5286b8d98f05%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHVpcTDnRUJModi6OyMmCOcCKR-5UbWhUQF6%2BpkAR6dQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline durability in GitHub Organization Project

[Mark Waite]

The durabilityHint symbol is provided by the workflow-job plugin.  Do you
have that plugin installed?

On Fri, Jul 12, 2019 at 6:04 AM Jan Kosecki  wrote:

> Hi,
>
> I've got a GitHub Organization Project that loads all requested
> repositories of the organization and builds them using Jenkinsfiles inside
> each repository.
> I've read this article https://jenkins.io/blog/2018/02/22/cheetah/ and
> I'm tempted to set dev builds to use "PERFORMANCE_OPTIMIZED" and only
> release builds to use "MAX_SURVIVABILITY".
> I tried to use "options { durabilityHint('PERFORMANCE_OPTIMIZED') }" like
> in article but it gets rejected by jenkins.
>
> Invalid option type "durabilityHint". Valid option types: [ansiColor, 
> catchError, checkoutToSubdirectory, lock, retry, script, skipDefaultCheckout, 
> timeout, timestamps, waitUntil, warnError, withAWS, withContext, 
> withCredentials, withEnv, ws] @ line 94, column 11.
>  durabilityHint('MAX_SURVIVABILITY')
>
>
> How can I set durability for different builds in GitHub Organization Project?
>
> --
> 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/da1bc51c-91b4-4e5f-885a-1396fe1f8e0f%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/da1bc51c-91b4-4e5f-885a-1396fe1f8e0f%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtELM1WQF0W4hdKG610d5-_tiC-nvX6A3WdzKUPgp06-%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: trying to get Jenkins pipeline to run across multiple nodes in parallel

[Mark Waite]

 sh '''
> echo "hostname: `hostname`"
> echo "whoami:`whoami`"
>
> '''
> }
> }
> }
>
> }
> }
> }
>
>
> But it's not dynamic, I need to have a stage per machine. Does anyone have a 
> suggestion
>
> about how I can achieve what I have in my original code?
>
> I want to dynamically decide what nodes to run the code on.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/b2ae506c-023e-4604-896e-50b4eac6d817%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/b2ae506c-023e-4604-896e-50b4eac6d817%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtHHOtUuej6vYzDhKbauCXq1w7qehM7UbMod4zGkfYYY9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline durability in GitHub Organization Project

[Mark Waite]

Are you running the most recent releases of the Pipeline plugins?  That
symbol was first included in workflow job plugin version 2.17.

On Fri, Jul 12, 2019 at 6:37 AM Jan Kosecki  wrote:

> Yes, I do.
> From what I see, "workflow-job" ID references "Pipeline: Job" plug-in chuj
> I have installed.
>
> On Fri, 12 Jul 2019, 13:10 Mark Waite,  wrote:
>
>> The durabilityHint symbol is provided by the workflow-job plugin.  Do you
>> have that plugin installed?
>>
>> On Fri, Jul 12, 2019 at 6:04 AM Jan Kosecki 
>> wrote:
>>
>>> Hi,
>>>
>>> I've got a GitHub Organization Project that loads all requested
>>> repositories of the organization and builds them using Jenkinsfiles inside
>>> each repository.
>>> I've read this article https://jenkins.io/blog/2018/02/22/cheetah/ and
>>> I'm tempted to set dev builds to use "PERFORMANCE_OPTIMIZED" and only
>>> release builds to use "MAX_SURVIVABILITY".
>>> I tried to use "options { durabilityHint('PERFORMANCE_OPTIMIZED') }"
>>> like in article but it gets rejected by jenkins.
>>>
>>> Invalid option type "durabilityHint". Valid option types: [ansiColor, 
>>> catchError, checkoutToSubdirectory, lock, retry, script, 
>>> skipDefaultCheckout, timeout, timestamps, waitUntil, warnError, withAWS, 
>>> withContext, withCredentials, withEnv, ws] @ line 94, column 11.
>>>  durabilityHint('MAX_SURVIVABILITY')
>>>
>>>
>>> How can I set durability for different builds in GitHub Organization 
>>> Project?
>>>
>>> --
>>> 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/da1bc51c-91b4-4e5f-885a-1396fe1f8e0f%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/da1bc51c-91b4-4e5f-885a-1396fe1f8e0f%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> 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/CAO49JtELM1WQF0W4hdKG610d5-_tiC-nvX6A3WdzKUPgp06-%3DA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtELM1WQF0W4hdKG610d5-_tiC-nvX6A3WdzKUPgp06-%3DA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> 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%2BroAGMPMqAnw7iojpJ%2BNDN%3DdUOWc_cNZJcv9jAPxpX2SwRGrA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CA%2BroAGMPMqAnw7iojpJ%2BNDN%3DdUOWc_cNZJcv9jAPxpX2SwRGrA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
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/CAO49JtE4apO_cBhBh2XeF81z_ubiYd9itYNitO_aoAk52pnnJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build failure in Jenkins: DependencyCheckAnalyzer

[Mark Waite]

I suspect that someone removed the OWASP dependency check plugin from your
Jenkins server.  That seems to be the plugin that is providing the
`dependencyCheckAnalyzer`
keyword for the domain specific language.

Alternately, has the plugin been disabled in your installation?

As another alternative, possibly there is some runtime bug that caused the
keyword to be removed from the DSL?  That seems unlikely to me, but I guess
it could be possible.

On Thu, Jul 25, 2019 at 9:18 AM Jason Flowers 
wrote:

> Nope
>
> On Thursday, July 25, 2019 at 9:48:28 AM UTC-4, slide wrote:
>>
>> Did anything get updated on your Jenkins instance?
>>
>> On Thu, Jul 25, 2019, 06:27 Jason Flowers  wrote:
>>
>>> I am getting a build failure in Jenkins with our maven
>>> dependencycheckanalyzer. This is a piece of code we haven't changed and was
>>> working for a long time and randomly started failing our builds yesterday..
>>> apart from commented out the code to run the dependency check, any idea on
>>> how to resolve?
>>>
>>>
>>> java.lang.NoSuchMethodError: No such DSL method 'dependencyCheckAnalyzer' 
>>> found among steps [ansiColor, ... ]
>>>
>>> --
>>> 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 jenkins...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/df0c1698-f90d-498d-b112-4541874328b5%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/df0c1698-f90d-498d-b112-4541874328b5%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> 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/9fea5d24-b69e-4f5b-b601-4e19243375b6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/9fea5d24-b69e-4f5b-b601-4e19243375b6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Thanks!
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/CAO49JtFhqGx9FswQErvKCpTGoEBgeLVZh0eFkaoYOUd5mnVCPA%40mail.gmail.com.

Re: Windows 7 Agents (slaves) via SSH

[Mark Waite]

On Thu, Jul 25, 2019 at 3:55 PM Steve K 
wrote:

> Hello,
>
> Has anyone successfully implemented the use of SSH to launch Windows 7
> agents (slaves)?
> I have been attempting to setup OpenSSH, but I'm falling short of getting
> it working.
> For one thing, the sshd never shows up as one of my Services, even though
> I believe I've followed the steps necessary to register the service.
> If I attempt to launch sshd manually, I get ACCESS DENIED, even though I
> can successfully launch ssh-agent.
>
>
I would not expect OpenSSH server to ever work with Windows 7.  It doesn't
work with the original releases of Windows 10.  Microsoft didn't make
OpenSSH server available until a relatively recent Windows 10 service
pack.  It has been working quite well for me from the Windows 10 service
pack on the 3 or 4 Windows 10 machines that I run.


> We have been happily using JNLP for our Windows agents, but, as we deploy
> Java 11 on our slaves, the JNLP method is no longer available.
>

Since you were using JNLP from a web browser previously, I assume that
means you were launching from a desktop login.  If you're launching from a
desktop login, then you can launch the agent with a batch file instead of
using JNLP.  That works with Java 11.

Don't forget that the Java version running the agent process must be the
same major Java version as the Java version running the master.  If you're
running Java 11 on your master, you need to run Java 11 on the agent.  If
you're running Java 8 on the master, you need to run Java 8 on the agents.


>
> Please share any tips and tricks you may have needed to employ to make the
> SSH slaves work as expected.
>
> Thanks in advance.
>
> Steve K.
>
> --
> 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/1298b6db-6dd5-4226-8d0e-f394e50e3077%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/1298b6db-6dd5-4226-8d0e-f394e50e3077%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Thanks!
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/CAO49JtF%2B4fYjd7o5eyBW_sS7i2RB8Cfwtg01ZiEiOz-ja0b7bQ%40mail.gmail.com.